Asset ids are not rendering full urls - ideas?

Hi there guys,


There seems to be something funky going on. We are running 4.2.1 (Heading to upgrade to 4.4.2)



Adhocly - assets are not rending full path urls correctly which creates a nightmare to our public users.



They are also for some reason grabbing CMS authoring urls instead of the production path.



Say for example (though not actual real examples - as we have fixed it for the moment) -



https://cms.site.com/?a=111111 would display on the front end rather than

http://www.site.com/path-to-url



It's really odd as the assets are linked correctly and showing the correct id's.





Anyone else had this adhocly happen and have ideas how to rectify?



Many thanks

Fuzzi

Hi,
Is your CMS authoring urls appearing above the production url in the Root url configuration? (System Configurations > System URL Settings > System Root URLs)

Also when the URL are not translated correctly is the web address visited same as the one when the URL are translated correctly? (protocol, query strings, etc,.)



Ash

I've had the same happen once before and it was due to coding the <a> tags incorrectly.
I accidentally wrote:

    text

Instead of:

    text

It was the missing period (.) after the opening quotes in the href attribute that caused the issue. Easy fix.

[quote]
Hi,

Is your CMS authoring urls appearing above the production url in the Root url configuration? (System Configurations > System URL Settings > System Root URLs)

Also when the URL are not translated correctly is the web address visited same as the one when the URL are translated correctly? (protocol, query strings, etc,.)



Ash

[/quote]



Hi Ash,



Thansk for getting bcak to me so quickly =)



I have just checked in the system config and yes the authoring url is higher than the production url. So is this possibly a cause?

When the urls are not translated correctly - they do infact bring up the authoring urls - but don't actaully print the url. The protocol is ok - it renders http://



Cheers

[quote]
I've had the same happen once before and it was due to coding the <a> tags incorrectly.

I accidentally wrote:

    text

Instead of:

    text

It was the missing period (.) after the opening quotes in the href attribute that caused the issue. Easy fix.

[/quote]



Thanks heaps for your reply. At first we though the same too and in we went with glee to be the savior of the day - but alas - no it wasn't.

Also a colleague mentioned that is seems to affect only affects specific divisional areas. So if one link was playing up in a div - all the links would also be affected within that div and display the cms urls with the id's.


It seems the only divs that are spared are the RAW_HTML divs.



I don't know if that puts a spanner in the works.

[quote]
Hi,

Is your CMS authoring urls appearing above the production url in the Root url configuration? (System Configurations > System URL Settings > System Root URLs)

Also when the URL are not translated correctly is the web address visited same as the one when the URL are translated correctly? (protocol, query strings, etc,.)



Ash

[/quote]





Hey Ash, I have just checked our QA environment and the production urls are higher.

So I susssppect along the lines these may have got out of sync from the production instance.

Hurrah!



cheers

[quote]
Hey Ash, I have just checked our QA environment and the production urls are higher.

So I susssppect along the lines these may have got out of sync from the production instance.

Hurrah!



cheers

[/quote]



Hi,

I was trying to write a detailed explanation as to how the URL is calculated/translated. But I am glad you have some lead on where to look at. Trust me the process of translation done by Matrix can get quite complicated to explain :wink:



But yea the bottom line is if you bump up the prod URL then you should be JUST fine.



Ash

[quote]
Hi,

I was trying to write a detailed explanation as to how the URL is calculated/translated. But I am glad you have some lead on where to look at. Trust me the process of translation done by Matrix can get quite complicated to explain :wink:



But yea the bottom line is if you bump up the prod URL then you should be JUST fine.



Ash

[/quote]



sweeeettttt =) Thanks again

Are you using the MyMatrix browser Plugin for MySource Matrix?


I have spent the last hour trying to troubleshoot a very similar problem and discovered if I disable the plugin the links are getting resolved properly again!



It seemed to mainly affect the WYSIWYG editor and using the HTML Source button to manually edit any of the HTML.




    Some Link

would get re-written to

    Some Link



Cheers Mat