New Asset Map displaying error messages

(K Dennis) #1

We have just upgraded our test system to Version 4.18.0, and enabled the new asset map.

 

We are seeing this error message flash when expanding to show child assets:

"string code asset_loading_node not found"

 

These error messages are permanently showing:

"STRING CODE ASSET_MAP_STATUS_COLOUR_KEY NOT FOUND"

"string code asset_map_tree1_name not found"

"string code asset_map_tree2_name not found"

 

and These show up on the right click new child menu

"string code asset_map_menu_teleport not found"

"string code asset_map_menu_refresh not found"

"string code asset_map_menu_no_previous_child not found"
"string code asset_map_menu_new_child not found"
 
I have noticed that the message flash when expanding is disappearing as we progressively access the various children.
 
Is anyone else experiencing similar behavior?
 
Can anyone suggest a fix, please?
 
 
 
 
 

 

(Nic Hubbard) #2

Can you try running the compile_locale.php script again?

#3

Elllo there,

we have upgraded to 4.18.0. You'll need to clear out cookies and cache on your browser before you access admin.

We had this and a clean up of the browser and all good =)

(Bart Banda) #4

Elllo there,

we have upgraded to 4.18.0. You'll need to clear out cookies and cache on your browser before you access admin.

We had this and a clean up of the browser and all good =)

 

Yep, I had to do the same thing. 

(Luke Wright) #5

For the translations issue, certainly it would be appropriate to clear the browser cache before using the Modern Asset Map for the first time.

 

The asset map translations are in the JavaScript component of the compiled translation files for the first time, whereas they used to only live in the Java component. Without clearing the browser cache, it's probable that you'd still have the old JavaScript translations from your previous revisions of Squiz Matrix, hence the "string code not found" missing translation strings you're getting.

 

Hope this helps.

 

Regards,

~ Luke

(K Dennis) #6

Thank you, Nic, Fuzzi81, Bart and Luke.

 

Clearing the Cache and Cookies in the Browser fixed it.

#7

Hey Luke!
This could be one for the technical manuals. Appologies if its already there !

(Luke Wright) #8

Hey Luke! This could be one for the technical manuals. Appologies if its already there !

 

Thanks for the suggestion - will look to put it into the release notes pages of 4.18rc1 and 4.18.0 - we normally put post-upgrade warnings like these into the release notes pages so they'll go there.

(Luke Wright) #9

Update: warning to clear browser cache now on the 4.18.0 release notes page: http://manuals.matrix.squizsuite.net/patches/4.18.0

 

It won't go into the RC1 page as upgrades to that were unsupported.

(K Dennis) #10

I think there is something else that needs to be done to get all of the translation strings working!

 

I say that because, following the successful upgrade of our test system we proceeded to upgrade the production system.

This time we cleared the browser cache as recommended above, and as expected *most* of the error messages disappeared. 

 

But not all of them.

 

Trying to find out why, I searched the codebase.  Using the example of the error message "string code asset_map_tree1_name not found", this what I found:

 

The string "asset_map_tree1_name" is not in the file "js_strings.en.js" (and I checked our working test system, which is no longer showing the error.)

 

The translation "Tree One"  for the string "asset_map_tree1_name" is only found in the file " lang_strings.xml" 

 

 

Anyway, while that searching was going on, we continued to work with the production server, adding pages, making things  live, changing others to "under construction" .

 

and after about 4 hours, all of a sudden, the remaining error messages disappeared.

 

So all in all we're pleased that it is all working well.

 

But we have no idea, what we did or what happened to make it work.

 

Thank you everyone for your help

 

 

(BTW: the string for "asset_map_tree1_name" is still not in the copy of  "js_strings.en.js" from the browser cache)

(Benjamin Pearson) #11

This sounds like you have a proxy like Squid sitting in front of your production system and not your testing system. Your sysadmin should be able to clear Squid cache. Hope this helps.