Upgrade 1.8.2 to 1.9.2 Problem

[phrique]

@phrique

Most times it would be start_level='2' like...

http://multiintech.com/defaultcontent/i ... e=top_left

That works OK if you only have two levels, but in some cases I'm looking at level 3.  I'm going to use it like that for now because it's certainly better than nothing, of course. 

[Dr.CSS]

That makes it start at the children of the active page, the children can have as many levels as needed and if one of them are clicked it's children will show, unless you ell it number_of_levels='1' which will only call the first level children, the collapse='1' will make it so the 3rd level children won't show unless their parent is clicked...

[phrique]

That makes it start at the children of the active page, the children can have as many levels as needed and if one of them are clicked it's children will show, unless you ell it number_of_levels='1' which will only call the first level children, the collapse='1' will make it so the 3rd level children won't show unless their parent is clicked...

It doesn't seem quite right...I'm sure I'm just doing something stupid that will occur to me later.  This is what I'm using:

{cms_module module='menumanager' start_level='2' collapse='1'  number_of_levels='1'}

If you go to the site (http://www.holytrinitweb.com) you can see the behavior, especially under the "Parish Information" menu.  How it's behaving right now is acceptable, but not exactly the desired effect. 

BTW, love the new look and behavior on the admin console.  It's fantastic.  Thanks for the help as well.

[Dr.CSS]

You missed the y in link ...

Add this to the horiz menu css, it will keep 3rd level from showing till hovered...

#primary-nav li:hover ul ul ul,

Side menu tag...

{menu start_level='2' collapse='1'}

[Dr.CSS]

Did you look in Module manager to make sure all extra modules are up to date?...

[dmaireroa]

I read all the comments from my last post. Is there any updates? If not, then I might go to plan B and do a fresh install which takes me ages to do

Thanks

[gardapro]

I had nearly the same problem. After deinstalling the Album module it worked fine.
You might want to try this to...

[Amendra]

Hello again,
after three weeks of intense testing I found the reason - by mere coincidence! It was the very old content type "newsmodule" which caused the menu manager to break.

It might help to understand that my database originates back to 2006 where this special content type was a valid type. With newer module versions this type was no longer supported, but the database harbored these pages silently ever since. And up to version 1.82 it was no problem at all because the menu manager simply ignored these old types.

A note to the developers: The new menu manager died at line 268 because the new object $tmpc was empty when it approached these specific old pages.

This could well happen too with other uninstalled oder simply deleted modules and thier special page types, like album, cataloger, content alias and others. The moment you uninstall oder delete a module and don't switch back all pages related to this type before deleting the modules, the pages may be invisible but not deleted. (The cataloger module does leave its own page content types in the database, I've tested it.) These pages might remain within the database and slumber there silently.

The page tree in the backend doesn't show them either, but there might be a hierarchy numbering inconsistency. New pages might get a hierarchy number higher than the older without the old and lower page numbers showing up. So a 3.2 immediateley follows the hierarchy number 3, whereas number 3.1 will remain invisible.

An invisible page is neither editable nor deletable. Even worse, all other pages relating to this page are invisible as well, and the parent page won't be deletable at all.

In my case, the older versions introduced an even more severe bug when adding a new page to the tree: A new page was numbered the same way like the old invisible page. So two pages shared the same hierarchy number. No problem for the old menu manager, completely unacceptable for the new one.

I saw two alternatives here: Delete the invisible old page directly in the database oder make it visible again by editing the content type and change it from "newsmodule" to content. The latter showed the page again in the page tree and got the menu manager working properly (yay at last!!) - but behold and beware: Another page (even two for me because I used the old module type twice) contained the same hierarchy number!

Correcting that was a pain in the a**. After a lot (and I mean "a lot") of pushing around both the old and the new pages within the page tree and into other chapters finally solved the hierarchy numbering problem.

How will you find old page content types if they remain invisible within the backend page tree?

You have to do this via phpMyAdmin (or any other mySQL editing software).
The appropriate mySQL command is:

Code: Select all

SELECT * FROM `cms_content` WHERE `type` != 'content' ORDER BY `cms_content`.`type` ASC

whereas 'cms_' has to be replaced by your database table prefix.

A list will show up with all page types that are not "content". page link, link, sectionheader, separator and errorpage are part of the standard types shipped with CMSms, others belong to modules, may they be active or not. You can then decide what to do with them.

Remember: If you choose to delete the pages by hand right in the database, you also have to delete all relating fields within the "cms_content_props" database table too, otherwise they will remain there forever.

Please do this only if you know what you are doing. And backup the database prior to any changes, of course

A request to the developers: If these old content types belong to your core functions or to modules you ship with your base/full version, then please find a way to notice a user within an upgrade process that these old content types still exist and can cause severe problems.

Or find a workaround within the menu manager module, as I did. As for the newsmodule type: I would suggest that you change the content type during upgrade and fix the duplicate hierarchy numbering problem...

Wow. Three weeks for one tiny little and very old issue...

Tired but content
Amendra

[musicscore]

This is what I did after have upgrade problems.

I made a backup of the database using mySqldump (CMS Made Simple version 1.8.2)
Did a fresh install of CMS Made Simple 1.9.2 and restored the database using mySQLdump module (all tables)

Check and all worked perfectly, althought restoring an old database in a new database version is not preferable.

Hope this works for all my CMS Made Simple friends.

PS. Don't forget to run the upgrade.php to upgrade the database (number) after the restore of the old database.

[gocreative]

I can't find the upgrade in the file release system. How do I upgrade v1.8.2 to the next version, then the next, and so on? I'd prefer to do it incrementally so I can pinpoint any issues.

[musicscore]

Download the new version from the cmsms website.
Then unpack the file and copy all the files to you server.
Overwrite the old files.
After copying all the files start your browser and go to {yoursite)\install\upgrade.php

Follow the instructions and there it is, you upgraded your website.

Donn't forget to remove the install directory.

BUT ::::

If you change files on your old site these files will be overwriten.
SO before you start MAKE A BACKUP.

Some tags or modules my have changed. Check the website after the upgrade and adjust.

[gocreative]

Does this apply to any version? i.e. Can I upgrade from any version to the latest version this way? I was under the impression that I had to work my way through the incremental update packages.

[Jos]

yes! This applies to any version. You can do your upgrade in one step. Might want to read this adventure by Uniqu3: http://www.i-do-this.com/blog/37/Advent ... to-1-9-4-1

[gocreative]

Great! Thanks everyone for your help.

[reneh]

Just a friendly reminder:
In general you can upgrade from any old version to latest by using the latest full install packet and use the upgrade function.
This can be done since all versions of CMS Made Simple (at least up to version 1.9.4.2) have all upgrade steps included in the full install packet. BUT this may change in future!

On other hand you must read the release notes (and changelogs) for ALL versions back to the version you upgrade from - to see if anything special have to be taken care of after the upgrade.

AND remember BACKUP! And be sure the backups are good.