I think you misinterpreted me as to regards of the WF-Section module. I am not just merely not changing a few lines of code or adding something else, I am basically in the process of re-factoring the code and I am pretty sure that when I am finished there will be too many differences between the versions.

I have pretty much removed much of the code that they added in for the reasons I stated above.

Plus, as someone once said, choice is sometimes good.

I'm doing this for my own personal use and yes, I am using that version as a starting point.

To be honest and very frank, I tried all the forums before I decided that the only way I was going to get what I wanted, was to recode it myself. Some of the changes in this version are nice, but some others will actually cause more problems than they will solve.

Also, the admin area is a complete and utter mess, and this goes back to just about every version I have used.

I also want to add in lots more administrator tools.

I have uploaded a working version to my site (Testing purposes) and you will see what I am aiming at look and feel wise.

http://www.xoosla.com/modules/newbb/

Depending on how I feel when it is finished and if I get enough requests I may release it.

I am currently re-developing CBB right now and I can honestly say I have never seen a module that has so many hidden features in my life and with no way of changing what should be a simple task as changing the title or text in this manner.

For example: there is a file called plugin.php in the include folder that has an array that gets merged with xoopsModuleConfig. yet, there is nothing special about these variables and really should have been added in the correct manner and this would make them easily accessible.

Not to cloud the issue, but how does this help her?

Quote:

In all honesty, I have never known the situation with modules to be as bad as this. Least before I knew where to go to get modules from. But with the collapse with many module developer sites, a lot of module are now left wanting and dead.

The repository has been like this for many years now and just like we have been told many times that things are about to change, they never do. I mean how long does it take to fix things here?

I would rather have a few working modules listed in the repository rather than a list of modules that are over 3 years old and do not work. How had is it to remove them from the list? How hard is it to find the latest version and list them?

Also, I think it would help to push module developers in the right direction here. Push them to use the repository in the correct manner and submit their latest releases there or have someone they can approach to help them with this.

Another issue that needs sorting is this, when does a minor change of code warrant being called a new module? For example: There was a time that there was about 10 different versions of WF-Sections going around, and all with minor changes to the code and something that could have been submitted easily as a patch or submitted to the developer.

This is why we need guidelines for submission. If someone submits a module that is just a small variant of another one, then it should be submitted as a patch and enforced as such.

My 1p on the matter

Hiya,

The IP restriction can be done with code modification to the core and database to properly work and what version of Xoops are you using now (As I know you upgraded earlier).

Also, what is the lines above

require_once XOOPS_ROOT_PATH.'/class/pagenav.php' ; at line 3?

The JSCal2 calendar has been removed from the next version (2.4.5) for the reasons you are asking about and has been replaced with a previous version.

I'm not sure about a JQuery version, but in reality I suppose that is the way Xoops should be looking I guess.

ATB

Catz

Quote:

The module has been written in such a way that is unobtrusive as much as possible. At the moment there are only two core files that have been modified and the changes should *Not* effect the normal working of the core if the XooslaCandy module is not used.

The more people that can test this for me the better it will be in the long run.

*NB* I have found a couple of issues that will require some changes to the module.

If you do not see a link under the textarea this can be for one or two reasons.

1. You have not selected which groups can have access to the Xooslacandy module. To do that go into the Xoosla prefs and select the groups that can use the Xooslacandy system throughout Xoops.
2. The Module that you are using does not use the Xoopseditor class for textarea and editing text. I will expand the system to use the other Xoopsform classes in the next issue.

ATB,

Catz

For the last few weeks I have been developing on the latest stable release and I have found many issues and bugs that could easily be fixed. But like many developers, I tend to work around the problem and code my own solution and I tend never to think about reporting the bug.

Now, I know that I am not alone here and today I decided to test on Xoops 2.4.5 and I found a bug that should have had module developers screaming 'We need this fixed'. I went to see if this had been reported and there was a fix and to my surprise, no one reported this, and the bug is still in SVN.

Now for those concerned about this issue, here is a link to it and you will see why this could be a major problem in the long run.

https://sourceforge.net/tracker/?func=detail&aid=3025455&group_id=41586&atid=430840

I would urge all developers to take sometime out to report a bug when they find one, rather than just finding a work around to the issue.

I urge all developers to bookmark this link and if you find a bug, please take 5 minutes of your time to track it and help out.

https://sourceforge.net/tracker/?group_id=41586&atid=430840

Thanks peeps :)

Hiya Xoopsers,

I have decided to release two new modules for testing. XooslaCore and XooslaCandy and I would be extremely grateful if you guys and girls could help out with their development.

Xooslacore is a total rewrite of the WF-Resources module, it is smaller, faster will help in the aid of Xoosla Module development in the future and providing many new features both for (Xoosla) developers and users alike. Automatic updates, stats on Xoosla modules and more.

XooslaCandy,

Xoosla candy was inspired by the Joomla modules, RokCandy by Rocket themes. Xooslacandy works in very much the same way but for Xoops. This module was basically just a test for the new Xoosla module framework and I thought that it could come in handy for Xoopsers out there.

For those of you interested, would you test both these modules out and provide some feedback, good or bad, just as long as it helps in the development process.

Warning:

Due to the nature of XooslaCandy, it was required that some core files be modified for proper working usage. Also, this module will only work with other modules that use the XoopsEditor framework or with the Xoops default editors. Anything else will most likely fail.

So if you wish to use this module, start annoying the developer of the module that doesn't implement either of these by default.

Instructions on how to install these modules and hacks are in the zip package.

Remember: These modules are considered as Alpha and are only released for testing purposes, as they may change heavily in the future.

Please download from Xoosla Modules

ps: These modules have only been tested on
1. Xoops 2.44,
2. PHP 5.2.3 + 5.3,
3. MySql v5 and
4. apache v2.2.11

Sorry for my poor grammar tonight,

ATB

Catz