I’m not sure what I did.
Here’s a quick history: I played with modx on my workstation. Now that I’ve gotten the site up and running I uploaded the modx asset, install, and manager files into the web site root from a new zipped install. I installed and sql’d in the site contents. I uploaded the assets that I was using and everything seemed dandy.
Now that I try to delete a document on the root folder I get pushed to the Event log. If I try to clear the event log I get the following error:
The document you are trying to delete is a folder containing document 5. This document is registered as the ’Site start’ document, and cannot be deleted. Please assign another document as your ’Site start’ document and try again.
So I’m a bit confused. I’ll end up restarting the install and database. I’ll copy and paste everything as if I didn’t have a modx install at all. Just thought you guys may want to discover what could have made things go crazy.
-
MODX Staff
- 10,725 Posts
That just means the initial page for your site is defined as the document you are trying to delete, which it prevents on purpose.
ibolmo - to clarify, is the error correct? Are you trying to delete either document 5 or a folder containing document 5? Did you try following the instructions in the error message?
Right this is an actual error. The file I’m trying to delete has an id of 30. The entry page has an id of 5.
So the script is confused.
Besides why would deleting something bring me up directly to the Events Log page??
I’ve mentioned that it gives me the error when I press: Clear event log. So why would that contain the entry page/folder ?
Intriguing. Is the date on the Event log the date of your delete-30 attempt, or an earlier date?
If you add another document and then delete it, do you get the same issue?
If you don’t mind PMing me your manager location and an admin-level user & password, then I can have a look.
ibolmo shared his details with me today. I can confirm what he is experiencing:
Whenever he tries to delete a page, it goes to the Event Log. At this stage it does not mention the id 5 thing, just some old messages about /installer still being present.
At any time, if he tries to clear the event log, including if he goes to the event log directly, MODx redirects to a page that gives the deleting id 5 error. So the id 5 is not directly related to the deletion of a document with id 30 or 23 or whatever.
This is in 0.9.2.2.
I have no idea what the heck is causing this, I suspect it’s a corrupted file somewhere given that no other 0.9.2.2. user has reported this issue.
If reuploading MODx, you might as well go straight to 0.9.5. RC3 as it is stable and certainly preferable to 0.9.2.2.
