2
Uid depend on what you prefer. Within my website and registered users the uid is very important and not the usergroup. After a year they can extend their registration. For this they have to give their uid, because this is a unique number for that registered person. For me easy to see as soon they have made their small payment. Because they have to menton their uid-number.
Why not use both (possibility) in future instead one or the other.
Why not use both (possibility) in future instead one or the other.
3
Dont know about which images we are talking, but if it are the overall in every module used basic images concerns like: edit, print, activate/deactivate, pdf, and so on, I prefer to put them in a central core image diectory. Outside directory module/MODULE/templates/images
It really makes no sense to upload al the same images many times within each and seperate module. If you would like to change some images you have to run through all the installed modules.
It really makes no sense to upload al the same images many times within each and seperate module. If you would like to change some images you have to run through all the installed modules.
4
Quote:
++2
Chance is that it will be also become confusing for not new xoops users. (think of theme and template and the frequently asked questions about this.)
As for releasing 2.6.0: Great job developers are doing. I feel trust is coming back to Xoops, which feels actually very good.
flipse wrote:
Quote:The extensions should reside in their own directory and not the module directory. It can be a little confusing especially to new users if an item is a module or extension.
+1
++2
Chance is that it will be also become confusing for not new xoops users. (think of theme and template and the frequently asked questions about this.)
As for releasing 2.6.0: Great job developers are doing. I feel trust is coming back to Xoops, which feels actually very good.
5
One great module I used for years. Due to the lack of further development I stopped using this module 2 years ago.
Glad to see this module now is picked up again and will be, hopefully one mature often used module (next to Publisher) within future Xoops version(s).
Thanks Mamba you took the effort for giving this module the proper and deserved attention.
grtz., Shine
One great module I used for years. Due to the lack of further development I stopped using this module 2 years ago.
Glad to see this module now is picked up again and will be, hopefully one mature often used module (next to Publisher) within future Xoops version(s).
Thanks Mamba you took the effort for giving this module the proper and deserved attention.
grtz., Shine
6
Are the above mentioned testresult fixed? This is not clear. It looks not if I see date and revis. nr. of this publisher module.
Any news on status of it?
Any news on status of it?
7
No offence, but I don't understand a &^%^$# of how transifex works. And really I don't feel like reading lots of readme's in trying to understand how and what I should do to work in it.
Dutch translation sais 99% ready. How can I see what the 1% is which hasn't been translated yet?
@DCrussader: don't forget you know exactly how transifex works. Don't get angry if others don't. And do not have the time to first read a complete bookwork before using this appliction.
I am sure more ppl are willing to help with translation, but are affraid of transifix because of unknown and not familiar with it.
For myself: no idea how it works, don't understand it at all and for trying: affraid of &^% it all up.
Last but no least: and where can ppl download translated packages?
Therefore I still keep translating (as many others) within notepad++ or editplus.
Dutch translation sais 99% ready. How can I see what the 1% is which hasn't been translated yet?
@DCrussader: don't forget you know exactly how transifex works. Don't get angry if others don't. And do not have the time to first read a complete bookwork before using this appliction.
I am sure more ppl are willing to help with translation, but are affraid of transifix because of unknown and not familiar with it.
For myself: no idea how it works, don't understand it at all and for trying: affraid of &^% it all up.
Last but no least: and where can ppl download translated packages?
Therefore I still keep translating (as many others) within notepad++ or editplus.
8
Quote:
++++++++++
Quote:
++++++
Quote:
++++++++
As an comment:
I see a lot of -'blue move'- modules appearing. They are placed within SVN. Bugs and fixes which are applied are sometimes fixed, sometimes not. It is unclear. BUt the module stays within SVN as a rar file.
Look at mymenus. Within topic stated as final, but still some major bugs aren't solved. Why call it final if it is still beta, of RC. ?
As i already mentioned earlier, I am getting more and more confused which modules are blue move ready, bug fixed/debugged after release. I hate SVN. If ready (Final) take it out of the trunk (for off. download), put it on xoops.org within downloadsection Category: Blue Move
No I have to spit through topics and read pages of pages to find the proper/lates grmbl trunk-SVN rar version.
Quote:
Totally agree. And every release gets the status Final. But no attention to given bugs (and sometimes suggested fixes).
And,...... keeping the same name of cloned modules, which results in even more confusion.
5. When you fork someone else work, please (no, no please anymore) RENAME the damn module, it's no longer the one created by the initial author.
++++++++++
Quote:
8. Every module must be packed with ZIP or 7Z, no rars, no crappy UHA or else unknown archiving formats or paid such as RAR.
++++++
Quote:
11. When u release a news story about your work, provide accurate mirroring on SourceFore.NET or Google Code, they're not going down like your shared hosting somewhere in Argentina or Mexico or Sudan. Add a link to support thread in forums on this site, ppl can't learn, speak and write in Every language on this planet, nor they to be forced to register everywhere to ask question or to submit bug report.
++++++++
As an comment:
I see a lot of -'blue move'- modules appearing. They are placed within SVN. Bugs and fixes which are applied are sometimes fixed, sometimes not. It is unclear. BUt the module stays within SVN as a rar file.
Look at mymenus. Within topic stated as final, but still some major bugs aren't solved. Why call it final if it is still beta, of RC. ?
As i already mentioned earlier, I am getting more and more confused which modules are blue move ready, bug fixed/debugged after release. I hate SVN. If ready (Final) take it out of the trunk (for off. download), put it on xoops.org within downloadsection Category: Blue Move
No I have to spit through topics and read pages of pages to find the proper/lates grmbl trunk-SVN rar version.
Quote:
Usually is like this, but here someone - just throw release after release without paying attention to discovered bugs or problems with they're work - wont mention nicknames anymore.
Totally agree. And every release gets the status Final. But no attention to given bugs (and sometimes suggested fixes).
And,...... keeping the same name of cloned modules, which results in even more confusion.
9
If all fixes have taken place and no other errors occur, then please take it out of SVN. make it a .zip/tar file and place within blue move 'ready' modules.
Otherwise we are getting lost with this module an ppl download wrong version(s).
Thanks
Quote:
Quote:
Otherwise we are getting lost with this module an ppl download wrong version(s).
Thanks
Quote:
Mamba wrote:
Thanks fixed in SVN
Quote:
Shine wrote:
BUG:
Short overview other submittions by user. Link to entry doesn't work. That is because de name of the module isn't picked up.
<{$link.module_dir}>/
should be: <{$wfllink.module_dir}>/
FIX:
File: templates->wflinks_singlelink.html
Line prox: 116
old code<{if $wfllink.otherlinx > 0}>
<br /><{$other_links}>
<{foreach item=link_user from=$link_uid}>
<div style="margin-left: 10px;"> <a href="<{$xoops_url}>/modules/<{$link.module_dir}>/singlelink.php?cid=<{$link_user.cid}>&lid=<{$link_user.lid}>"><{$link_user.title}>a> (<{$link_user.published}>) div>
<{/foreach}>
<{/if}>
Replace with:<{if $wfllink.otherlinx > 0}>
<br /><{$other_links}>
<{foreach item=link_user from=$link_uid}>
<div style="margin-left: 10px;"> <a href="<{$xoops_url}>/modules/<{$wfllink.module_dir}>/singlelink.php?cid=<{$link_user.cid}>&lid=<{$link_user.lid}>"><{$link_user.title}>a> (<{$link_user.published}>) div>
<{/foreach}>
<{/if}>
10
Have fixes, after release, taken place?
If so, please don't let it be within SVN trunk as a .tar file. Make it zip or rar file.
Tar give lots of problems if you don;t have the proper free unzipper for it.
I have to say I get more and more lost with al the SVN trunk files.
If so, please don't let it be within SVN trunk as a .tar file. Make it zip or rar file.
Tar give lots of problems if you don;t have the proper free unzipper for it.
I have to say I get more and more lost with al the SVN trunk files.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Sep 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|