I try to edit the main wiki description box, and when i try i get
What does this mean?
There were some problems with your submission:
Invalid revision specified. Cannot use as the current revision.
I try to edit the main wiki description box, and when i try i get
What does this mean?
There were some problems with your submission:
Invalid revision specified. Cannot use as the current revision.
What is the URL path it sends you to? e.g. /wiki_index.php?do=save
- lead developer for VaultWiki
Yes, and on that screen it gives me that error.
This means that there were errors saving the revision that the DM was unable to detect ahead of time. When it tries to get new revision from the database to flag as the new version of the page, it finds out it doesn't exist.
This is not supposed to be possible. I've added a free service to the Members area for you. Please fill it out and I will have a look.
- lead developer for VaultWiki
Ok i filed it out, also i do have vbseo installed, and it should be running good enough, but would prefer not give admin access until i have to.
Okay, your index is fixed now. Somehow the revision ID wasn't set correctly in the database on the index page. I don't know how this is possible, unless you had a database error or fatal error another time when you were saving the page (most likely when the page was first created). I have looked at the code over and over and can't see a reason why this would happen only on your install, or at all, without another error to trigger it.
If there are other showstopper errors you noted during the install that you didn't already report, please let me know. Maybe it was something as simple as trying to proceed to the 'creating_wiki_index' step when the wiki content-types weren't in the database. This might have made vB give an 'invalid content type' error, or something like that.
Perhaps we may never know.
I have modified the editor UI for Alpha 3 so that fields are not arbitrarily set if they are detected not to have changed (or in this case, the default-fields are set, when the exists-fields were already set). This should bypass the error if it ever happens to other users.
- lead developer for VaultWiki
I really appreciate the help, looking forward to the new version. >8)
Bookmarks