Updating the content of MNTP when republishing on a new domain
Scenario: Let's say we've build a website on testweb.whatever.dk and we used several MNTP's throughout the site. Now we wanna move the website to staging.whatever.dk, but a lot of links are still using the old domain when browsing the website.
I've tried using this one: /Umbraco/dialogs/republish.aspx?xml=trueand it works for most of the links. But it looks like that all links generated by the MNTP are not updated.
How do I force a complete update of the entire website ?
I'm not sure I follow completely - MNTP only stores ID's - so you're very likely to have a macro of some sorts actually generating the actual links, right?
Obviously you haven't got any hardcoded domains in there (since Save & Publish works) but could it maybe be a caching issue?
Yeah - I'm still wondering - the only thing I can see would be that the MNTP references a Widget type or similar that's using the URLPicker data-type - that one stores a URL along with the id, and if you're using the URL directly (instead of using NiceUrl() with the node-id), this would be the exact scenario you'd encounter.
Updating the content of MNTP when republishing on a new domain
Scenario: Let's say we've build a website on testweb.whatever.dk and we used several MNTP's throughout the site.
Now we wanna move the website to staging.whatever.dk, but a lot of links are still using the old domain when browsing the website.
I've tried using this one: /Umbraco/dialogs/republish.aspx?xml=true and it works for most of the links.
But it looks like that all links generated by the MNTP are not updated.
How do I force a complete update of the entire website ?
I'm running on a Umbraco 4.9.0
The site has around 1000 nodes, so Save & Publish on each node is not an option :)
You could republish every node programmatically?
Hi Sebastian,
I'm not sure I follow completely - MNTP only stores ID's - so you're very likely to have a macro of some sorts actually generating the actual links, right?
Obviously you haven't got any hardcoded domains in there (since Save & Publish works) but could it maybe be a caching issue?
/Chriztian
-- Just ignore this reply ;-) --
@Chriz: All the XSLT Macros have 'Cache By Page' enabled. But that's by default.
Yeah - I'm still wondering - the only thing I can see would be that the MNTP references a Widget type or similar that's using the URLPicker data-type - that one stores a URL along with the id, and if you're using the URL directly (instead of using NiceUrl() with the node-id), this would be the exact scenario you'd encounter.
Alas, please ignore me if that's not the case :-)
/Chriztian
@Chriz: You are the frekking man. When you use the _MultiNodePickerHelper.xslt that is exactly what happens :)
Did you add a testweb.whatever.dk as a domain in the back office when you where testing? Thats the only reson i can think of
Noooooo ... I marked my own post as the solving answer ... not very karma like. #h5is
Ha - cool!
Use the urlpicker-helper.xslt as well, and you'll never have that problem again :-)
(For the record: _MultiPickerHelper.xslt just delegates to your own templates for the Widgets :-)
/Chriztian
is working on a reply...