Thanks so much for this report.

I have been struggling for days to diagnose a problem with my local test site running under WAMP which does not occur (thankfully) on my live website. I have a button in one of my modules which downloads a dynamically constructed XLSX file, and this suddenly started to hang the server. In addition, the Preview buttons on my DHTML Text Area fields started to report "Server Not Responding ... Please Try later".

After completely reconstructing all my self-signed certificates (the live server has a real certificate), and updating my local Apache logging, I realized that almost all requests to the local test site were returning a 404 status, but the pages themselves were still rendering normally. I got some minimal success by changing the code to force a 200 status when returning the preview text and my XLSX file. But still the Software Engineer in me needed to understand why this functionality suddenly stopped working.

My local test server is a development platform and as such it has several Xoops modules installed which are not on the live server.
I had installed xSitemap (1.56 Final) intending to use it to build a list of all my pages as I transition the site to Xoops 2.5.11 and Bootswatch 5.3. This report encouraged me to look more closely at what was installed on the local test site. When I discovered that both xmnews and xSitemap had the new index.php files mentioned in this post, I uninstalled them as a test. And suddenly things were back to normal.

After some additional tracing and testing, I offer the annotated segment from my Apache access log which clearly demonstrates that there is something about xSitemap when installed in Xoops 2.5.10 that causes the erroneous 404 status in the Http Response.


The scenario is as follows:
1. Start with a clean install of Xoops 2510
2. Install xSitemap and press the button to go to the website Home Page
At this point accessing the website still returns a 200 status.
3. Close the browser and reopen the website
At this point almost all requests return the 404 status.

Installing xSitemap in Xoops 2.5.11 does not have the same result.

The xmnews module does not seem to have the same effect, so I do not think the index.php files could be causing the problem. I have done exhaustive debugging through the site startup with xSitemap installed and I can't see anything that might shed any light on the cause. But something in xSitemap is not playing well with Xoops 2510.

@Mage

Thanks!

To celebrate the 3 years of work on XOOPS 2.5.11 (and yes 3 years today), we have decided to propose an article per week on the modifications of this version. The objective is to analyze a period to highlight statistics and important points of modification.

You can find article 1 here:

https://www.monxoops.fr/modules/xmnews/article.php?news_id=49&lang=english

Awesome and impressive work, as always!!!

Kompozit Paletler

Modules Used

- Publisher
- Xmcontent
- Contact

Xoops Version 2.5.10

Demo:
http://paletec.com.tr/

There are always two kinds of people in Open Source:

1) Those who come and see opportunity to help and contribute

2) Those who come and always complain, without contributing

Sadly, Sophie2 is a perfect example of the second group of people. She came after many years of absence, she trashed the project in order to feel better about herself, and then she left.

XOOPS is Open Source, i.e. it is up to the people to contribute and make it better. Nobody is stopping anybody from forking XOOPS from Github, contribute to it, and make it better!

Paraphrasing John Kennedy: "Don't ask what XOOPS can do for you, ask what YOU can do for XOOPS"

hi Sophie2
hi xiran

I'm not understanding why you are not satisfied with XOOPS

What kind of a niche would you like to be filled by XOOPS?
What kind of progress would you expect?
If the code is a problem, what would you suggest?
Dou you have visions of a modern CMS?

@xiran

I agree and it's pretty obvious. No new users, barely a community and just maintenance of the old concepts to death.

The code itself and the github activity is the least of the problems Xoops has, I think.

There's no vision (at least not properly presented) and I can't even imagine some young new web developers coming to this website and getting excited about Xoops.

I checked in to see if there's at least something left here from the good old days, but it appears everyone is perfectly fine with the way things are so I will see myself out.

Hey Mamba,
same time, same thought, same answer

lol xiran,
Are you blind ?
See https://github.com/XOOPS/XoopsCore25/graphs/contributors?from=2014-06-15&to=2022-02-22&type=c