Before you address the primary issue, I have a registration question. We just launched a site today that uses Toolset, hidden link, but the Toolset key is for the staging URL. Where can I change this key and register the live URL? I know how to generate a new one in the account dashboard.
Second, the client sent over a News item with just a community name, which I found out is also the Community slug (I was not the developer on this site). There seems to be a conflict with permalinks. I renamed the News post to something else, but now the community slug, /community/ellingsworth-commons, is being redirected to the news post. I put the news post into draft mode, but the Ellingsworth Community cpt slug is still redirecting to the native WP post in News (blog article). I purged the site and theme cache, and I am still having an issue. I saw a support thread where the URL slug can be customized under options/rewrite. Can you be more specific for my sake.
Thanks,
Melody
We just launched a site today that uses Toolset, hidden link, but the Toolset key is for the staging URL. Where can I change this key and register the live URL? I know how to generate a new one in the account dashboard.
Hi, there isn't a mechanism for editing an existing key so you'll delete the old key, create a new key and register the new URL. The best process is to log into your account and go to https://toolset.com/account/sites, where you will delete the existing key. Nothing will break and the performance of the site will not be impacted by deleting this key, but automatic updates will be disabled until you register. Then log into your new site's wp-admin panel and go to wp-admin > Plugins > Add New, and click the "Commercial" tab. Scroll down to the Toolset installer panel and click Unregister the Site. Again, nothing will break and the performance of the site will not be impacted by unregistering a live site. The page will reload. Now click Register Toolset, and you'll see a link to "get a key for this site". Clicking that link will redirect you to the toolset sites page, and generate a key for the correct URL so there is no confusion with typos, http vs https protocols, etc. Copy that new key and paste it back in wp-admin to register successfully.
There seems to be a conflict with permalinks. I renamed the News post to something else, but now the community slug, /community/ellingsworth-commons, is being redirected to the news post.
Simply renaming the post does not always update the permalink, just to be clear. You may need to manually change the permalink as well.
It's possible the browser has cached the redirect as well, which can be confusing. As a test, please try visiting the Community post in a different browser like Chrome or Firefox to verify the redirect is happening on the server-side and not just in the browser. If the redirect happens in a different browser as well, then it is confirmed there is some kind of permalink conflict.
You mentioneed you purged the site and theme cache. Did you also resave the site permalinks in wp-admin > Settings > Permalinks? Choose a different format temporarily, save the changes, then choose the desired format again and resave those changes to flush the rewrite rules.
I saw a support thread where the URL slug can be customized under options/rewrite. Can you be more specific for my sake.
This feature gives you the ability to specify one post type slug in wp-admin, but use a different slug in the permalink structure, like "communities" instead of "community", for example. So in wp-admin your post type slug would be 'community', but in the front-end your CPT post URLs would be something like
https://yoursite.com/communities/post-title-1
https://yoursite.com/communities/post-title-2
https://yoursite.com/communities/post-title-3
etc. You can configure this in Toolset > Post Types. Edit the Community CPT and toggle open the "Options" panel. Under the Rewrite option, select "Use a custom URL format" and enter the alternate slug like "communities" or whatever you choose in the input field. Whether or not this will help in your case is not really clear to me based on the information I have so far.
Feel free to provide updates here and we can discuss further.
Simply renaming the post does not always update the permalink, just to be clear. You may need to manually change the permalink as well.
-- I changed the URL slug for sure. That is fixed. After I made my ticket, I saw a thread that said that I had to go back and re-save the permalinks options under the WP settings. That flushed the settings.
You can configure this in Toolset > Post Types. Edit the Community CPT and toggle open the "Options" panel. Under the Rewrite option, select "Use a custom URL format" and enter the alternate slug like "communities" or whatever you choose in the input field. Whether or not this will help in your case is not really clear to me based on the information I have so far.
-- So if I am understanding this, I would go to the post type, look under OPTIONS, change it from using the WP logic to custom, and I understand all of that ... but, am I using /communities/ or just communities, no slashes before or after? Also, they will be wanting the 2 News articles published. Can I change the native permalinks back to /%category%/%postname%/ for native blog posts, or leave it as is? This will be something we will see over and over I am sure.
but, am I using /communities/ or just communities, no slashes before or after?
No slashes or other URL elements, just communities
Also, they will be wanting the 2 News articles published. Can I change the native permalinks back to /%category%/%postname%/ for native blog posts, or leave it as is? This will be something we will see over and over I am sure.
Sure you can, you can set it however you want and address problems in the future as they arise. There is nothing to stop you or anyone else from creating category terms with slugs that are identical to custom post type slugs, and nothing to prevent you or anyone else creating ambiguous post title slugs. Some problems are unavoidable when using this format, unless you implement custom code solutions that prevent ambiguous URLs.
My issue is resolved now. Thank you!
