I started moving a site from one web host to another last week, and went ahead and installed a fresh version of Evo 1.0.6 on the new server before I moved the database over. One thing I noticed today is that when I create a new resource under a container resource, the Menu Index value is always 0. In 1.0.5, the Menu Index would auto-increment as you added resources.
Is this something that changed in 1.0.6, or is it possibly a result of the way I moved the data to a fresh install of modx? Or is there a setting that I've completely forgotten about to toggle this behavior? Many thanks.
Edit: As an additional note, my new database is MySql 5.0.95. I ran across an old forum post saying that earlier versions of 5.0.X had bugs that broke some DB queries. I can't sort by menuindex using Ditto now either. Is this related? Like Modx just can't see the menuindex field, so that's why it always sets it to 0?
[ed. note: althenry last edited this post 14 years, 5 months ago.]
Try Tools > Configuration > Site > Menu indexing default
;) KP
-
☆ A M B ☆
- 24,524 Posts
hmm... I do believe I see a new page for my "MODx From the Inside" e-book, "How MODx Configuration Settings Work", with full documentation on each setting option. That should keep me occupied for a while!
The sad part is that I did look over the configuration tabs like 5 times, and yet I still managed to miss it.
Well, I was 99.9% certain the setting existed, but it still took me 5 mins to pin down its exact whereabouts. Maybe some rationalization of the Config layout could usefully be included in the "Evo revival" project?
;) KP
-
☆ A M B ☆
- 24,524 Posts
Lots of relatively minor fixes to be done. For example, having some TinyMCE configuration done in the Site Configuration and some in the Plugin's Configuration.
