Missing TagManager on 3.10

Squiz Matrix Installation
1

This was going to be a post asking for help, but I managed to resolve the issue. I thought I'd post it here in case anyone else ever has a similar issue:


We've recently upgraded a client system from 3.6.4 to 3.10.1.



Everything appeared to have gone smoothly, until we tried to move a page.



At that point, the HIPO job stalled at 10% and we got the following errors:



While the HIPO was running:

    19:45:53 - 28 Sep
    User: Root User (5)
    Level: MySource Warning
     (/core/include/locale_manager.inc:513) - Asset #8578 is not a tag_manager [SYS0089]
     
    Raw Entry:  [28-Sep-2006 19:45:53] PHP Fatal error: Call to a member function on a non-object in /home/websites/v3_rcn_intranet/core/hipo/jobs/hipo_job_create_links.inc on line 893



What is interesting her is that the errors are quite correct "Asset #8578 is not a tag_manager ". 8578 is actually a File asset.

This asset ID is being pulled from /data/private/conf/system_assets.ini , but is obviously incorrect.

A look in the database indicates that there is actually not a tag_manager asset in the system:
    v3_rcn_intranet=# select assetid from sq_ast where type_code = 'tag_manager';
    assetid
    ---------
    (0 rows)




(From Avi: I have removed the resolution from this post because I believe there are more critical issues here, like why the Tag Manager wasn't created in the first place. I also suspect the upgrade process used may have been incorrect and I don't want to mislead any other users).
2

Are you able to reproduce this bug? Can you use a backup of their previous version on a test server, re-do the upgrade and see if you get the same result?


Also, while upgrading from 3.6, you did upgrade to 3.8 first before going to 3.10, right? If not, you should have! Upgrades should go through each major version. Skipping 3.8 is very bad juju.

3

[quote]Are you able to reproduce this bug? Can you use a backup of their previous version on a test server, re-do the upgrade and see if you get the same result?


Also, while upgrading from 3.6, you did upgrade to 3.8 first before going to 3.10, right? If not, you should have! Upgrades should go through each major version. Skipping 3.8 is very bad juju.

[right][post=“12160”]<{POST_SNAPBACK}>[/post][/right][/quote]



I will try it on a test system from the backups later.



It went through 3.8. In fact it went through pretty much all the minor versions between as we had problems on upgrades when not doing this.

4

[quote]It went through 3.8. In fact it went through pretty much all the minor versions between as we had problems on upgrades when not doing this.
[right][post=“12176”]<{POST_SNAPBACK}>[/post][/right][/quote]



Ok, very thorough. :slight_smile: You shouldn’t have to go through all the minor versions, as long as you do all the steps required by each minor version upgrade. Here if a client wants to upgrade from 3.6 to 3.10, we take them to 3.6.8 first, then to 3.8.6, then 3.10.1.



It would be good to see if you can reproduce the bug so that we can fix it. :slight_smile: