It's ridiculous to hear this. If you want something to progress, show what is it that you can do good.

These type of accusations from people who have left the community a long time ago have no value, as you are doing nothing to make part of it and show the good work you can do to make a change.

Progress will not happen bickering around like hungry dogs over thoughts that have been born from corrupted minds.

Fortunately while ones are away in their bickering, there's a greater community behind, with a more professional attitude, STILL working.

This is because of the cache feature that your changes don't show up. You can login to your administration panel and go to system > preferences > general settings.

Check to yes this option: Check templates for modifications ?

When you've finished doing changes to the theme check it back to no.

This will refresh the template cache stored in templates_c folder.

You can check out Anatomy of the Default Theme, although the current default theme has been updated to use modules below content, it can give you a general idea.

There's an updated theme.html with the new smarty variables at < this link >, it would have been much better if it was done without tables, yet it will use the styles of the current default theme. Basically you use this and create a stylesheet for it or use the default style.css as starting point. All the layout is managed through adding id's or classes to your html and defining them in your stylesheet.

Bluestocking, I do appreciate much your interest at contributing at the wiki. I saved the post you did at < this link >, so it's not going to be erased from the wiki site, but the discussion tab will probably be removed. Managing discussion threads is much easier in the forum.

The reason I told you to ask your main questions here at the XOOPS forum is because the wiki is conformed by people who wish to be documentators of XOOPS and I saw that your questions were focused to the area of managing the addons structure. So for the people that are managing the addons site, it would be much easier for them to see your questions here than there at the wiki.

I am learning to use the wiki as much as the other people, but at the wiki forums I'll be glad to assist you in working out ways to make the layout of your document be as you want.

So for creating a template for specific document, you are welcome to post a discussion about this at the wiki forum.

For asking about modules, the place would be here at the XOOPS forums.

Thank you for contributing to this process.

I see the wiki site up. There has been problems with slowness of the server, but the site is open and everyone is welcome.

This is following on from Bender's work in gathering module descriptions. - to ask the community for help in preparing new descriptions for the forthcoming repository update.

There has been a new area created at xoopswiki.org in the Projects section (english) called Repository Redevelopment

A list of the modules with information will be listed on this page on the Wiki, complete with links to the relevent XOOPS forum post, ALL current descriptions done by the community have been migrated there.

For an example of how to complete each entry, please see these forum posts

All new module descriptions should be done in the wiki, the forum Repository: A list of modules will be closed.

If something about the modules must be discussed this should be continued to be done in the xoops.org forum: File repository - Maintenance since the wiki forum is ONLY for making announcements of new documentation projects being created and to talk about the wiki document structure and NOT for XOOPS discussions.


For anyone who wishes to assist with this - please note the following:

1 - You will need to be on this page:
http://www.xoopswiki.org/modules/mediawiki/index.php?title=Category:Repository_Redevelopment

2 - Type the module name in the "create article to this category" box

3 - Paste the following template in the newly created page: Module description template and fill in the relevant information.

4 - Please DO NOT erase, this should be kept at the end of the page : category:Repository Redevelopment

This is following on from Bender's work in gathering module descriptions. - to ask the community for help in preparing new descriptions for the forthcoming repository update.

There has been a new area created at xoopswiki.org in the Projects section (english) called Repository Redevelopment

A list of the modules with information will be listed on this page on the Wiki, complete with links to the relevent XOOPS forum post, ALL current descriptions done by the community have been migrated there.

For an example of how to complete each entry, please see these forum posts

All new module descriptions should be done in the wiki, the forum Repository: A list of modules will be closed.

If something about the modules must be discussed this should be continued to be done in the xoops.org forum: File repository - Maintenance since the wiki forum is ONLY for making announcements of new documentation projects being created and to talk about the wiki document structure and NOT for XOOPS discussions.


For anyone who wishes to assist with this - please note the following:

1 - You will need to be on this page:
http://www.xoopswiki.org/modules/mediawiki/index.php?title=Category:Repository_Redevelopment

2 - Type the module name in the "create article to this category" box

3 - Paste the following template in the newly created page: Module description template and fill in the relevant information.

4 - Please DO NOT erase, this should be kept at the end of the page : category:Repository Redevelopment

quoting Madfish
"Edit: Cross post, sorry Snow."

No problem Madfish, we are all here sharing our points of view, and even if similar, each point of view is just as valuable. What's important is the interaction in between us all as long as it's done with nice manners.

[edit]

The way I understand things, although I may be mistaken. I agree with Tom, Herko and Peekay; and the decision of taking it away from public here at XOOPS were people already have the module and are using it is a mistake. McNaz, is a good developer, and with great respect he has the free will to do with it what he wants and license it in any way he wants but in a new version.

http://www.gnu.org/licenses/gpl-faq.html#CanDeveloperThirdParty
Can the developer of a program who distributed it under the GPL later license it to another party for exclusive use?
No, because the public already has the right to use the program under the GPL, and this right cannot be withdrawn.

http://www.gnu.org/licenses/gpl-faq.html#HeardOtherLicense
I heard that someone got a copy of a GPL'ed program under another license. Is this possible?
The GNU GPL does not give users permission to attach other licenses to the program. But the copyright holder for a program can release it under several different licenses in parallel. One of them may be the GNU GPL.

The license that comes in your copy, assuming it was put in by the copyright holder and that you got the copy legitimately, is the license that applies to your copy.

http://www.gnu.org/licenses/gpl-faq.html#CanIDemandACopy
If I know someone has a copy of a GPL-covered program, can I demand he give me a copy?
No. The GPL gives him permission to make and redistribute copies of the program if he chooses to do so. He also has the right not to redistribute the program, if that is what he chooses.

As far as I know I have a copy (v0.93) and so do hundreds of other people. I don't see anywhere in the files a license just in the xoops_version that it says GPL.

If it was taken away from XOOPS repository it was respecting in a humane way McNaz's decision, but under GPL terms this is incorrect in my opinion, unless the module has a different kind of license in the packaged zip.

Quote:

Template overriding is used to place an edited module template inside the themes folder and create your own "template set", it's not to do with the theme itself, it just keeps the templates in one accessible place inside the theme folder. I find it as a "safer" way to keep control over module template editing.

Also with the module XOOPSinfo you can keep track of which templates are being overridden.

My recommended option is to use the Template Overriding technique instead of template cloning.