Changed ID in phpmyadmin now auto increment is going from that ID

so i thought it would be a cool thing to make my error page ID 404. Well now all new pages are 405 406 etc. so i went back into phpmyadmin and i set the ID back to 3 4 5, etc.. but now it still auto increments from 404 +

am I doomed? is there anyway I can reset the increment counter? (Is DocManager available for Revolution or something similar?)

thanks!

What exact command did you run?

You don’t WANT to set it back to 3 or 4... the primary key increments up, one at a time, so if you left successfully reset the counter to 5, it’d overwrite all your posts (6,7,8,...). To reset the counter, you’d have to delete the table. If I were you, I’d just leave it alone. You dodged a bullet -- you poked around at the internals in a way you never should, and thankfully your site still works. Be grateful you didn’t screw things up.

I went into phpmyadmin and changed the value of the row "ID" for my 404 page to "404" so I only have 2 or 3 resources in the site ATM. so my site goes 1,2,3, 404, then 405, 406

so i changed 404 to 4, 405 to 5, and 406 to 6. so now when I make a new page it becomes 407 but I want it to be 7.

I am ok with taking the risk of destroying the site as its only got one page on it and i haven’t done any work on it yet. I just wanted to get my counter reset back to normal. I know there has to be another value somewhere that controls the increment, wonder if anyone knows where that would be in the tables of the DB

ok i fixed it. I went into PHPmyadmin and i backuped up just the table modx_site_content

then i emptied the table and just imported that table back and its auto incrementing from 6 now instead of 406

As you found, you generally don’t want to mess with the ID numbers. No front-end user will ever see them and you can always get to the 404 page with:



or in code, with:

cool. yeah I’d never actually want to "goto" the error page. I just thought it would be cool to organize my manager with the error page as 404. just a cosmetic thing i am just glad its fixed

on a side note, I converted a site from modx 1.0.5 to Revo 2.0.8 and man its NOT fun can’t wait to see that migration assistant cause I have 10 - 20 clients with EVO 1.0.5 sites

Quote from: zurie at Feb 26, 2011, 07:25 PM

...cause I have 10 - 20 clients with EVO 1.0.5 sites

Parable:
EVO = Ubuntu (not Win XP, as it’s dead and buried)
REVO = Win Vista* (works nice when you have >3 Gb RAM**)
//* REVO isn’t Win 7 yet - BUT IT WILL BE!
//** Hosting Power

Message:
If your clients are happy running Ubuntu, there is
no need to upgrade them to Vista at this time.

EVO has evolved through all of these releases:
...
0.9.5,
0.9.6,
0.9.6.1,
0.9.6.2,
0.9.6.3,
0.9.6.3-RC1,
0.9.6.3-rc2,
1.0-pre1,
1.0-pre2,
1.0-pre2.1,
1.0-pre3.0,
1.0-pre3.1,
1.0-pre3.2(rev270),
1.0.0,
1.0.0-rc-1,
1.0.0-rc-2,
1.0.0-rc-3,
1.0.1,
1.0.1-rc-1,
1.0.2,
1.0.3,
1.0.4,
1.0.5

I think many people don’t know this...
The next upgrade from 1.0.5 doesn’t have to be REVO.
» » » http://bugs.modx.com/projects/evo/roadmap#Evolution-1.1.0 !

yeah but the point you are missing is that the general populous see’s one thing.. the finished product. but I, the web developer have to use the backend to build the sites. so it makes more sense for me to start using REVO 100% and then I can share snippets, plugins, code, and create new ideas and plugins. its easier to support one platform (revo) than to support half on 1.0.5 and half on 2.0

Awesome MODX spirit!
Many let their clients run the site using the backend though.

I’m not saying that you shouldn’t upgrade to REVO.

if (you have a great host == true) { DO IT!! }
else { EVO http://modxcms.com/forums/index.php/topic,57222.msg327665.html#msg327665 }

Quote from: zurie at Feb 26, 2011, 09:02 PM

yeah but the point you are missing is that the general populous see’s one thing.. the finished product. but I, the web developer have to use the backend to build the sites. so it makes more sense for me to start using REVO 100% and then I can share snippets, plugins, code, and create new ideas and plugins. its easier to support one platform (revo) than to support half on 1.0.5 and half on 2.0

Good point. Once you have the tools and the skills, Revo packages are actually easier to create and document, IMO. It’s hard for me to contemplate creating a new extra for Evo knowing that I can’t create a transport package so that non-techie users can easily install and configure it. I suspect that I’m not the only developer to feel that way.

The advice to non-techie users that Evo will be easier for them is somewhat misleading in certain cases. SPForm is a good example. The Evo install instructions go on for pages - downloading and unzipping the files to the correct locations, creating the resources, snippets, and chunks, pasting the correct code into them, editing the config file, etc., and there are many ways to go wrong. For Revo, the instructions are: "download through Package Manager, "click on install." and "enter your email address." Ten seconds later, you have a working contact form on the site.

And don’t forget that the Revo Manager is extremely customizable for clients who need a simple UI.