- This topic has 16 replies, 2 voices, and was last updated 1 month, 1 week ago by David.
September 26, 2020 at 10:05 pm #1460509Ian
For both GP and GPP, I was running 1-2 versions behind the latest Betas. I have now updated to the latest beta builds, could not find anything in search so hoping someone may know here. Have been using Block Elements to hook in something to specific pages. Once setup, they work nicely. But when I go in to make an edit to the block, I see all but a few pages are targeted. The rest show Page = “blank”. Because of this, the blocks are being hooked on random pages on the site. Hoping someone ran into this and this was fixed in the latest beta releases? New site is a few days from going live! Thanks gang!September 27, 2020 at 12:37 am #1460612Ian
Update: Running GPP 1.12.0-rc.1 and GP 3.0.0-beta.2. Same issue. When I go back to edit the Block under Elements, only the first 5 pages are still targeted. All other previously targeted pages are blanked out. And clicking on the Dropdown to target a page also brings up a blank. Had to remove all targeting and start again. Odd.September 27, 2020 at 4:24 am #1460783DavidStaffCustomer Support
can you try rebuilding the peramlinks – by clicking Save in the Settings > Permalinks.
If still an issue – are you using Custom Links or any other plugin that changes permalink behaviour?September 27, 2020 at 2:41 pm #1461432Ian
Maybe we are getting our wires crossed. Not sure what Permalinks has to do with the issue at hand but just in case, I re-ran Permalinks. The issue still exists.
From here, you can see I have set 17 pages for this block to show up via Elements. When I set things up for the first time, they display properly on the site: https://www.dropbox.com/s/nw7mx0n2i2cf3p8/elements-issue-01.jpg?dl=0
Now the problem show up when I go back to Edit the Element. You will see all the pages are now blank except for the first few.
The only resolution I have found is to make edits to the Block, delete all those Blank Pages as it won’t allow for page selection any longer, re-create a new rule for each of those pages again. It’s cumbersome and dangerous when someone else just goes in and edit the Elements without manually re-targeting everything. The Block was displaying randomly throughout the site until I deleted all blanks and re-created the rules.
Hope that helps to clarify the issue. Any thoughts?September 28, 2020 at 1:30 am #1461816DavidStaffCustomer Support
It was a shot in the dark in case something had messed with permalink/slugs and therefore the list was no longer relevant.
We have had only a couple of similar reports of this, its usually related to very long lists of display rules – but never been able to replicated locally.
How many pages do you have in total ? And what determines the requirement for the Block Element?
Maybe we can look at a better solution for managing them.September 28, 2020 at 6:06 am #1462111Ian
Right now, I have 2 Elements and both show the same issue. One has 17 Pages and the other 20 pages. They are Block – Hook targeting “generate_after_content”. Just trying to hook a block at the bottom of specific pages.September 28, 2020 at 6:59 am #1462184DavidStaffCustomer Support
Maybe this solution will work for you:September 28, 2020 at 7:40 am #1462236Ian
Interesting. So if I understand that correctly, this would add a custom field in Posts and Pages so when the client can choose to attach this page to a specific Element? If so, this may work. But I do think it’s best to actually find the cause and fix the original issue. For now, I will just have to live with manually re-creating the page targeting every time I have to update that Element. Not the best way but it’s ok for now. Hope you guys find a fix in the near future. Thanks!September 28, 2020 at 7:49 am #1462387DavidStaffCustomer Support
The tricky part with the missing/broken display rules is its inconsistent – we only had a couple of reports of this and we have not been able to replicate it. But it is something we are mindful of and we’re looking at the many reasons why it may occur. If we do identify it as a bug, as opposed to a localised issue, then we will address it.
That proposed solution registers a new taxonomy called ‘Post Element Control’ the UI in the post editor will be the same as Categories and Tags. All it requires is you create a separate term for each of your elements.
Eg. Hero Element, Footer Element.
Then assign those as your Display Rules eg.
Post Element Control > Hero Element
Then any post you add
Hero Elementas term will automatically display the Hero Element.
Keeps display rules down to a single location and allows you to control the display from within the post editor.
Its something we’re looking at as a future feature of elements.September 28, 2020 at 9:50 am #1462567Ian
Thanks David. Noted. Appreciate your help on this one.September 28, 2020 at 3:32 pm #1462919DavidStaffCustomer SupportOctober 22, 2020 at 6:14 pm #1500622Ian
Something painful happened today and thought I would circle back to see if there have been any other reports of this disappearing Elements targeting. An element was updated today and 60% of the targeted pages disappeared from the list again. Could not even re-target them until I deleted ALL targeted pages, Saved, then edited the Block Element again and started to add in all new Page targets again. Painful. Luckily I had a list of the pages that were targeted as this was a known issue. Was hoping there was some headway in this by now?October 23, 2020 at 2:49 am #1500938DavidStaffCustomer Support
We have had no further reported issues of this happening, and we are still been unable to replicate the issue locally which makes it impossible for us to identify why a couple of users are experiencing this.
Did you try the other method i proposed ?October 23, 2020 at 12:39 pm #1501703Ian
So the idea is to create a new taxonomy in addition to Category and Tag? If that’s the case, what’s the best way to create this?
Also, the disappearing targets are all pages and not posts. I have always had a difficult time creating a tag for pages as there really isn’t a standard way to do this in WordPress.
Any help would be appreciated.October 23, 2020 at 2:56 pm #1501816DavidStaffCustomer Support
This topic explains how:
- You must be logged in to reply to this topic.