452
You can't fork it because you already have a fork of a fork (i.e. from me) - see the background here.
You have few choices:
1) the simplest one - you can delete my fork, and then fork the original XoopsCore25. Since you have access to all repositories in the chain of forks, you can set locally separate branches for different forks, work on a particular branch, and then make a PR to that repository (see how the author of the above question solved it).
2) There is also a more complex solution, if you want to keep separate forks, see: Create Multiple Forks of a GitHub Repo
I would recommend the option 1
You have few choices:
1) the simplest one - you can delete my fork, and then fork the original XoopsCore25. Since you have access to all repositories in the chain of forks, you can set locally separate branches for different forks, work on a particular branch, and then make a PR to that repository (see how the author of the above question solved it).
2) There is also a more complex solution, if you want to keep separate forks, see: Create Multiple Forks of a GitHub Repo
I would recommend the option 1
453
I have some fixes in XoopsFormRendererBootstrap5.php for Xoops 2.5.11, but GitHub says "No more forks can be created." when I try to fork XoopsCore25 in order to create a pull request. Do you want me to contribute these changes some other way?
454
Hello, if your php version is PHP 7.3+ and above, you will not get this error.
REQUIREMENTS:
- XOOPS 2.5.10
- PHP 7.3+
For a working demo of the module
https://erenyumak.com/ato/modules/countdown/
https://erenyumak.com/ato/modules/countdown/event.php?id=2
REQUIREMENTS:
- XOOPS 2.5.10
- PHP 7.3+
For a working demo of the module
https://erenyumak.com/ato/modules/countdown/
https://erenyumak.com/ato/modules/countdown/event.php?id=2
455
Hello,
I download the files and changed the folder name to countdown. As I try to install the module and find error occurs. How can I fix the problem? Thanks.
-- Failed to execute xoops_module_pre_install_countdown
Xoops 2.5.10
PHP 5..5.26
MariaDB 5.5.43
I download the files and changed the folder name to countdown. As I try to install the module and find error occurs. How can I fix the problem? Thanks.
-- Failed to execute xoops_module_pre_install_countdown
Xoops 2.5.10
PHP 5..5.26
MariaDB 5.5.43
456
Quote:
No, that's not correct.
XOOPS 2.5.11 works correctly with index.php in the /preloads folder, because it excludes it automatically.
The only problem with index.php in /preloads folder is with XOOPS 2.5.10 and older. So if you're using XOOPS 2.5.10, replace the index.php in /preloads folder with index.html that contains:
You should check on GitHub for the latest versions of your modules:
https://github.com/orgs/XoopsModules25x/repositories?type=source
On February 20th, we have updated several of the modules that included the index.php in /preloads and replaced it with index.html, so they would still work on your XOOPS 2.5.10 installation.
If you still have issues, please let us know.
So modifying the Xoops 2.5.11 autoload process to exclude the index.php file was not the resolution, and now all modules that use preloads must use the index.html file and not index.php for protection in their preloads/ directory. Is that correct?
No, that's not correct.
XOOPS 2.5.11 works correctly with index.php in the /preloads folder, because it excludes it automatically.
The only problem with index.php in /preloads folder is with XOOPS 2.5.10 and older. So if you're using XOOPS 2.5.10, replace the index.php in /preloads folder with index.html that contains:
<script>history.go(-1);script> You should check on GitHub for the latest versions of your modules:
https://github.com/orgs/XoopsModules25x/repositories?type=source
On February 20th, we have updated several of the modules that included the index.php in /preloads and replaced it with index.html, so they would still work on your XOOPS 2.5.10 installation.
If you still have issues, please let us know.
457
OK. That clears things up. I can imagine it took a long time to find the issue. I've been at this over a week, with much Apache research and several frustrating sessions with Wireshark before I clued in that the 404 was bogus.
So modifying the Xoops 2.5.11 autoload process to exclude the index.php file was not the resolution, and now all modules that use preloads must use the index.html file and not index.php for protection in their preloads/ directory. Is that correct?
Thank you so much for your work here.
So modifying the Xoops 2.5.11 autoload process to exclude the index.php file was not the resolution, and now all modules that use preloads must use the index.html file and not index.php for protection in their preloads/ directory. Is that correct?
Thank you so much for your work here.
458
The problem is relatively simple. The .php files which are in the "preloads" folder are loaded automatically by xoops. When we moved from index.html to index.php, we modified core (2.5.11) to not include the index.php file. But on version 2.5.10 there is no this modification.
Including the index.php file generates 404 errors (not in navigation) but on robots or internal scripts on the site.
Several weeks ago, I discovered that one of my websites was no longer referenced by google, the robots were blocked (error 404). I searched (very long) and found this problem. It is for this reason that all modules are modified with index.html in the "preloads" folder.
On xoops 2.5.11 there is no problem but before yes...
Including the index.php file generates 404 errors (not in navigation) but on robots or internal scripts on the site.
Several weeks ago, I discovered that one of my websites was no longer referenced by google, the robots were blocked (error 404). I searched (very long) and found this problem. It is for this reason that all modules are modified with index.html in the "preloads" folder.
On xoops 2.5.11 there is no problem but before yes...
459
Yes, indeed the xsitemap (1.56 FINAL) module does have the preloads/index.php file and replacing it with the preloads/index.php file from the profile module cures the problem. Thank you.
I had suspected the issue was with something in the autoload mechanism, but not fully understanding the details there, I could not make any specific connection. Would you be able to explain why the index.php file with its setting of the header status causes problems whereas the index.html file which just updates the history does not? Where do these files fit into the startup sequence?
Thanks again for your assistance.
I had suspected the issue was with something in the autoload mechanism, but not fully understanding the details there, I could not make any specific connection. Would you be able to explain why the index.php file with its setting of the header status causes problems whereas the index.html file which just updates the history does not? Where do these files fit into the startup sequence?
Thanks again for your assistance.
460
Hi, The problem most likely comes from the index.php file which is in the preloads folder.
Can you verify that the modules/xsitemap/preloads/ folder does not contain the index.php file?
If in this folder there is the index.php file, it is absolutely necessary to remove it and put the index.html file in its place.
You have to check all your modules and do the same manipulation.
The problem should go away.
Can you verify that the modules/xsitemap/preloads/ folder does not contain the index.php file?
If in this folder there is the index.php file, it is absolutely necessary to remove it and put the index.html file in its place.
You have to check all your modules and do the same manipulation.
The problem should go away.
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|