32
No, your username has not been changed. You simply have two accounts.
And when you submitted your email address to reset the password that you forgot, you submitted email to the other account ("bleekk_user"), and not your main account ("bleekk"), so the link you received from XOOPS automatically pointed to "bleekk_user"
I just sent you an email with more details.
And when you submitted your email address to reset the password that you forgot, you submitted email to the other account ("bleekk_user"), and not your main account ("bleekk"), so the link you received from XOOPS automatically pointed to "bleekk_user"
I just sent you an email with more details.
33
Hi everyone!
My username changed from "bleekk" to "bleekk_user". Do you know why?
I noticed it when I couldn't login and tried to reset my passwort.
Can you change it back to bleekk?
Thank you
My username changed from "bleekk" to "bleekk_user". Do you know why?
I noticed it when I couldn't login and tried to reset my passwort.
Can you change it back to bleekk?
Thank you
35
Hi,
I'm using xoops 2.5.11 behind Nginx Proxy Manager (https://nginxproxymanager.com/)
Nginx Proxy Manager has "Block Common Exploits" enabled for this proxy host
When you access to any page where in the url is present the parameter XOOPS_TOKEN_REQUEST you receive "403 Forbidden openresty"
Mostly in the System admin pages, I was using the block page when I found it
I'm not saying it is an bug in xoops or in Nginx Proxy Manager but since I want to keep "Block Common Exploits" enabled I need to hack xoops.
The problem is the presence of the word _REQUEST in the url
the following instructions will change that word in the xoops installation
I suggest to backup the files before to change them
change XOOPS_TOKEN_REQUEST in XOOPS_TOKEN_REQUE
include/findusers.php
modules/system/templates/system_notification_list.tpl
modules/system/templates/system_notification_list.html
modules/system/templates/blocks/system_block_notification.tpl
themes/xswatch4/modules/system/blocks/system_block_notification.tpl
change '_REQUEST' in '_REQUE'
class/xoopssecurity.php
class/xoopsform/formhiddentoken.php
I'm not using protector, maybe there is something to change also there
In preference I have: "Check templates for modifications? YES" otherwise I think you have to rebuild the templates
that's it
Carlo
I'm using xoops 2.5.11 behind Nginx Proxy Manager (https://nginxproxymanager.com/)
Nginx Proxy Manager has "Block Common Exploits" enabled for this proxy host
When you access to any page where in the url is present the parameter XOOPS_TOKEN_REQUEST you receive "403 Forbidden openresty"
Mostly in the System admin pages, I was using the block page when I found it
I'm not saying it is an bug in xoops or in Nginx Proxy Manager but since I want to keep "Block Common Exploits" enabled I need to hack xoops.
The problem is the presence of the word _REQUEST in the url
the following instructions will change that word in the xoops installation
I suggest to backup the files before to change them
change XOOPS_TOKEN_REQUEST in XOOPS_TOKEN_REQUE
include/findusers.php
modules/system/templates/system_notification_list.tpl
modules/system/templates/system_notification_list.html
modules/system/templates/blocks/system_block_notification.tpl
themes/xswatch4/modules/system/blocks/system_block_notification.tpl
change '_REQUEST' in '_REQUE'
class/xoopssecurity.php
class/xoopsform/formhiddentoken.php
I'm not using protector, maybe there is something to change also there
In preference I have: "Check templates for modifications? YES" otherwise I think you have to rebuild the templates
that's it
Carlo
36
XOOPS 2.5.11 should work OK with PHP 8.2.
The upcoming XOOPS 2.5.12 is being tested on PHP 8.4
Individual modules are a different story, some of them might have some issues.
The upcoming XOOPS 2.5.12 is being tested on PHP 8.4
Individual modules are a different story, some of them might have some issues.
37
Hi everyone,
I’ve recently started managing a small website built on XOOPS, and I’m slowly learning the ropes. One topic I keep seeing come up is cybersecurity, especially as open-source platforms can sometimes be more exposed if not maintained properly.
I came across a list of Cybersecurity Interview Questions and Answers while doing some research, and it made me realize how much I still have to learn. Some of the questions touched on CMS vulnerabilities, SQL injection, and proper permission settings—all things that seem highly relevant to XOOPS.
So I wanted to ask: What are some basic steps I should take to secure my XOOPS site? Are there plugins or modules you recommend? I’m especially curious if anyone here has created a checklist or guide for best practices in this area.
Would really appreciate any advice or resources you can share. Thanks in advance for helping a newbie stay ahead of any security issues!
Best regards
I’ve recently started managing a small website built on XOOPS, and I’m slowly learning the ropes. One topic I keep seeing come up is cybersecurity, especially as open-source platforms can sometimes be more exposed if not maintained properly.
I came across a list of Cybersecurity Interview Questions and Answers while doing some research, and it made me realize how much I still have to learn. Some of the questions touched on CMS vulnerabilities, SQL injection, and proper permission settings—all things that seem highly relevant to XOOPS.
So I wanted to ask: What are some basic steps I should take to secure my XOOPS site? Are there plugins or modules you recommend? I’m especially curious if anyone here has created a checklist or guide for best practices in this area.
Would really appreciate any advice or resources you can share. Thanks in advance for helping a newbie stay ahead of any security issues!
Best regards
39
Just chiming in to say I ran into a similar issue after trying to upgrade from 2.5.10 to 2.5.11 on a dev site. The front end loaded fine, but after logging in, I kept getting a blank white page. Turns out it was a module compatibility problem — in my case, an older version of the "Profile" module didn’t play nice with the new core files.
What helped was enabling debug mode via mainfile.php and also checking /modules/system/class/gui/. I replaced it with the default one from the XOOPS 2.5.11 release and things started working again.
Might be worth checking your PHP version too.. I had better luck running it under PHP 7.4 rather than 8.0 for now. Some of the older modules still throw deprecation notices under newer versions.
Hope that helps someone else running into the same wall!
What helped was enabling debug mode via mainfile.php and also checking /modules/system/class/gui/. I replaced it with the default one from the XOOPS 2.5.11 release and things started working again.
Might be worth checking your PHP version too.. I had better luck running it under PHP 7.4 rather than 8.0 for now. Some of the older modules still throw deprecation notices under newer versions.
Hope that helps someone else running into the same wall!
40
Thanks for sharing this update. I've been using XOOPS for several projects, and it's great to see ongoing discussions and improvements. Looking forward to more enhancements in the future.Quote:
Mamba wrote:
Please test MyMenus 1.54 Beta 10
Changelog:
- add option to use font awesome icons (liomj/mamba)
- fix cloning of links (liomj/mamba)
- fix return to the same menu after delete of links (mamba)
- escape column names with backticks (mamba)
- fix pagination of menus (liomj/mamba)
- add new skins: imageonly, xswatch4 (liomj)
HELP NEEDED
We'll need some help from designers to do some magic with the skins.
Some of the skins seem to be outdated, so we need a refresh:
a) fix those skins that are fixable
b) remove the skins that are totally outdated
c) add couple of new and attractive skins
Who could help us with it?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | AU$15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | AU$0.00 |
| Net Balance: | AU$0.00 |
| Left to go: | AU$15.00 |
 |
|