ReadyTheme link token and Legacy SEO Settings

[kayakbabe]

Question - when was this Update Navigation Set Item URLs added? What are the best user practices for this feature?

Inquring minds what to know too!

[lesliekirk]

...run the "Update Navigation Set Item URLs" scheduled task.

Question - when was this Update Navigation Set Item URLs added? What are the best user practices for this feature?

[kayakbabe]

I think it has been! I will!

[ILoveHostasaurus]

I'll just delete them out Kelly. You should come to MivaCon next year, seems like a decade since we've caught up.

[kayakbabe]

...

[lesliekirk]

We can work around this via htaccess to re-introduce the store code to the URL in the appropriate spot when using legacy rewrites. If you'd prefer to go that route just shoot me an email.

Thanks, David, I went old school. Only about a dozen links were affected. It was much easier to hard code them than to mess with settings and the htaccess file. Once the big fix is out, I can roll back to use the ReadyTheme Navigation Sets.

[ILoveHostasaurus]

Hey David,

Thanks - if I do that, what impact will it have on SEO? All of the current links have the Store Code in them. Wouldn't that break all the links out in the wild?

Leslie

We can work around this via htaccess to re-introduce the store code to the URL in the appropriate spot when using legacy rewrites. If you'd prefer to go that route just shoot me an email.

[lesliekirk]

I have no idea on the impact of SEO, you may want to open a support ticket so someone more knowledgeable can help you with that. As far as not breaking links, that could probably be fixed by modifying the .htaccess file to still support URLs formatted in that fashion.

No worries - I went old school and temporarily hardcoded the broken links

[dcarver]

I have no idea on the impact of SEO, you may want to open a support ticket so someone more knowledgeable can help you with that. As far as not breaking links, that could probably be fixed by modifying the .htaccess file to still support URLs formatted in that fashion.

[lesliekirk]

I've reproduced this issue and have filed a bug. As for a workaround, you could uncheck "Always include Store Code in URL" and then run the "Update Navigation Set Item URLs" scheduled task. (This will only work if your domain has 1 store.)

Hey David,

Thanks - if I do that, what impact will it have on SEO? All of the current links have the Store Code in them. Wouldn't that break all the links out in the wild?

Leslie

[dcarver]

I've reproduced this issue and have filed a bug. As for a workaround, you could uncheck "Always include Store Code in URL" and then run the "Update Navigation Set Item URLs" scheduled task. (This will only work if your domain has 1 store.)

[lesliekirk]

After more digging. This started right after the most recent update - Houston we have a bug!

[lesliekirk]

Is there a workaround for this token not including the Store Code when using the Legacy SEO Settings? The token is used in the ReadyTheme Navigation sets.

&mvt:navigationitem:link;

Legacy SEO Settings

(All of these are checked)

Enable Short Links
Always include Store Code in URL
Include Product Page Identifier in Breadcrumb Links

URL Delimiter: /

Prefix: Page

Suffix: None

Product Page Identifier: PROD

Category Page Identifier: CTGY

There are two results using this token

CTGY links produce a Fatal Error: Unable to open store 'CTGY'

Page links go NTFD.html (the message "We're sorry but it appears that the "NTFD.HTML" page is not available at this time.")