You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are running into issues where changing permalink in Wordpress is not reflected on Gatsby. We need to manually run Clean Cache and Build on Gatsby cloud which is very manual and need to remember every time there is a change to permalink structure.
What I did:
Went to wp-admin/options-permalink.php and set the structure to Custom: /ourname/%postname%/
What I expected to happen:
When I push the branch to gatsby cloud, it generates pages with the URLs that follow the /ourname/slug structure
What actually happens:
Gatsby continues to generate the URLs the existing way until cache is cleared and rebuilt
Additional info:
We also see the records are being added to the table for Permalink change
Raw Log after changing Permalink
When I 'Clear Cache and build ' on Gatsby Cloud, the URL's are updated correctly.
Please let me know if you need additional info to reproduce.
The text was updated successfully, but these errors were encountered:
Summary
We are running into issues where changing permalink in Wordpress is not reflected on Gatsby. We need to manually run Clean Cache and Build on Gatsby cloud which is very manual and need to remember every time there is a change to permalink structure.
What I did:
Went to wp-admin/options-permalink.php and set the structure to Custom: /ourname/%postname%/
What I expected to happen:
When I push the branch to gatsby cloud, it generates pages with the URLs that follow the /ourname/slug structure
What actually happens:
Gatsby continues to generate the URLs the existing way until cache is cleared and rebuilt
Additional info:
We also see the records are being added to the table for Permalink change
Raw Log after changing Permalink
When I 'Clear Cache and build ' on Gatsby Cloud, the URL's are updated correctly.
Please let me know if you need additional info to reproduce.
The text was updated successfully, but these errors were encountered: