2
Those are not events but callbacks. Events are those triggered through the XoopsPreload object, added from 2.4.0.
3
It would be very helpful for module developers if some more events like below be added to the system module:
Event: Triggered when a user account is deleted
Args: XoopsUser
Event: Triggered when a module is installed
Args: XoopsModule
Event: Triggered when a module is uninstalled
Args: XoopsModule
Event: Triggered when a module is updated
Args: XoopsModule
Event: Triggered when a user account is deleted
Args: XoopsUser
Event: Triggered when a module is installed
Args: XoopsModule
Event: Triggered when a module is uninstalled
Args: XoopsModule
Event: Triggered when a module is updated
Args: XoopsModule
4
Just wanted to let you all know that we have released the first beta version of our release. The version number of this release is XOOPS 2.0.10 JP Beta and available for download from the following sites.
http://www.xoopscube.jp/xoops/download.php
https://sourceforge.jp/projects/xoops/files/
The primary goal of our project is to provide fully secure, simple (light-weight), and scalable web application for all XOOPSers around the world. What we can say for now is that we're currently concentrating on making the 2.0.x JP releases secure and getting rid of any possible vulnerabilities found in the previous releases. A detailed roadmap is coming soon as well and will be announced shortly.
# I wasn't going to post this message here, however since I am getting lots of messages and was requested to reply here, I am doing so to hopefully make things clear for some people..
http://www.xoopscube.jp/xoops/download.php
https://sourceforge.jp/projects/xoops/files/
The primary goal of our project is to provide fully secure, simple (light-weight), and scalable web application for all XOOPSers around the world. What we can say for now is that we're currently concentrating on making the 2.0.x JP releases secure and getting rid of any possible vulnerabilities found in the previous releases. A detailed roadmap is coming soon as well and will be announced shortly.
# I wasn't going to post this message here, however since I am getting lots of messages and was requested to reply here, I am doing so to hopefully make things clear for some people..
5
I do not know right now what the real cause of your problem is, but 2.0.9.2 is not still 100% compatible with php5. Also you may need to downgrade MySQL to 4.0.x.
6
Those who have already upgraded to 2.0.9.1 can simply overwrite your XOOPS with the files included in 2.0.9_to_2.0.9.2. However there might be some minor problems with the uploader and the block administration. If you do have problems with them, you can do the following:
Uploader problem: apply the patch posted by Mith on this thread or simply replace class/uploader.php with the one included in 2.0.9.
Block administration problem: edit and save all your blocks. If you have already done that when upgrading to 2.0.9.1, I am afraid you would need to that again.
Uploader problem: apply the patch posted by Mith on this thread or simply replace class/uploader.php with the one included in 2.0.9.
Block administration problem: edit and save all your blocks. If you have already done that when upgrading to 2.0.9.1, I am afraid you would need to that again.
7
You can use the patch, but don't upload the files under html/modules/newbb if your site is using the newbb2 module, and not the one included in the core package.
8
This is not the problem of xoops, but the server configuration. Or perhaps you need to upload the files to a different directory (somewhere under /users/navinpcfreak.com?). You should ask the server admin to fix this.
10
Try adding back the categories as they were and change their category ids (look into the topics table and see what category ids the undisplayed topics have). Then I think hte topics would come back to be displayed.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|