-
Hello,
On top of the Local Patterns page I still have a button with the text “Legacy Pattern (6)”. When I click on it I get to a page with wp-admin/edit.php?post_type=gblocks_templates at the end of the URL and the error message “Invalid post type”.
Is this because I disabled Legacy Patterns when I didn’t remove them first or something like that?
Can this be harmful (with the upcoming new version(s) of GB in mind)?
Is there a way to undo/fix this and make the Legacy Patterns button disappear?GPP 2.5.0
GB 1.9.1
GBP 1.7.1 -
Hi there,
May I see a screenshot of the legacy pattern button?
You can upload it to your site’s media library or upload it to https://postimages.org/ and share the link with us?
Let me know 🙂
-
Shure, here it is: Screenshot
-
Oh, I see, you don’t need to worry about the legacy patterns, they were your local legacy pattern, and they will still work even after updating GB to 2.0.
-
But that’s exactly my point, the Legacy Patterns don’t work anymore. When I click the button I get a blank page with only an error message, as I mentioned in my first message. Something went wrong during the transition to the new Patterns. It seems like the old Patterns still exist (in the database), but they are no longer accessible. I don’t need the Legacy Patterns themselves anymore and I would like to clean them up ((if they exist somewhere)).
-
When I click the button I get a blank page with only an error message, as I mentioned in my first message.
I haven’t heard about this issue, may I have your site’s admin login and check the error in the backend?
-
I think the Legacy Patterns used a different post type than the current Patterns. This old post type has probably been deleted, but the posts still exist and that’s what the button refers to. Something like that.
The admin login is attached.
-
This is abnormal, as even if there’s no legacy pattern, it should still show with GB 1.9 and GB Pro 1.7.
I wonder if there’s a plugin conflict, any chance you can disable all other plugins to test?
-
I don’t think Legacy Patterns will remain accessible/visible (even if there aren’t any) after you disable them with the “Enable Local Patterns” button in the Generateblocks settings.
After you disable this button, the old post format will (partly?) disappear and the WP Patterns core post format will be used permanently, if I understand your documentation correctly. Also, the whole item “Pattern Library (Legacy)” with the two buttons “Enable Local Patterns” and “Enable Remote Patterns” in the GB settings will then disappear.
But if you disable the “Enable Local Patterns” button while there are still Legacy Patterns present, you will probably get the situation I have now, I think?
I cannot disable plugins, but I’ll make a copy of the site and experiment with it locally.
-
I can confirm that the issue is indeed caused by disabling “Enable Local Patterns” while Legacy Patterns are still present.
I was able to test this with an old local site with Legacy Patterns and where the button was not yet disabled. After I did disable the button, I got the same situation as the site you saw yourself.
I searched the database for “gblocks_templates” (which is the old post format) and found the Legacy Patterns that I previously saw in the backend. After I removed these from the database, everything in the backend appeared as it should be, without any references to the “Legacy Patterns” (because I had disabled them permanently).
This solved my problem, but would there be a way to achieve this without having to edit the database directly?
-
Hi there,
thanks for reporting this issue. I’ll mark this as a bug.
Is it ok if we keep the temporary login you provided so we can test ? -
Because this is a client website and I don’t want to take any risks, I made an exact copy on another domain, see the Private information. Username and password are unchanged.
With this copy you can test as much as you want.Thanks for your attention.
-
Thank you, that is much appreciated – we will reply here once we have a resolution!
- You must be logged in to reply to this topic.