Hi guys,
Was making what I thought was a standard edit to a MODx site today.
Pasted in an iframe into a document and saved. After saving the manager lost all styling (IE its just frames with no images and default fonts)
The home page of my site now reads:
"ERROR: Too many forward attempts!
The request could not be completed due to too many unsuccessful forward attempts."
I’m running MODx 0.9.6.3
Apache
PHP 5+
Tried following another post where the error page was not set, but my site has a site start, error and auth page set, but still problems. Any idea why the manager has caved in on me?
Going to try an upgrade, hopefully it will help.
Cheers,
Justin
Hi guys,
Tried an update to 1.0.4 but it failed.
For some reason the installer has blanked my config file. It’s empty when I open it?
Anyone any suggestions?
J
Update: Put a config in there myself, same problem. Manager is messed up and the homepage tells me too many forward attempts again?
Following on from the other tread I have tried to echo out whats going on in the sendForward function to see what is going on.
It appears the $id getting sent in is always null, hence the reason the else fires.
Anyone know why this is happening, and why the manager is all messed up?
Update: OK so I could not find out the cause, I just went and restored files and the DB from my backup server.
Everything appears to be back to normal.
Still a little worried that this problem literally came out of nowhere!
I added a piece of code and saved a resource....and BAM.
I’m worried this might happen again, and possible to a client site.
Guys there is something really weird going on here.
OK so it would appear that saving any document causes the problem described above. Upon saving the following is happening:
- The site cache is getting cleared.
This appears to trigger the problem mentioned above. Once I restore the site cache from my backup the site starts working again fine....
Obviously an update as failed, not sure what I can do now?
OK I figured out what was going on. Not a MODx fault but a problem with the hosting package I was running it on.
The account had reached its disc space limit, so when I tried to save and update the cache, the cache was getting completely blanked as the OS was not letting MODx write the cache files.
That killed the site.
I was able to increase the limit and refresh the site, and it all worked well.
Lesson learned!
