Skip Navigation

[Resolved] Custom archive pages do not open builder screen to properly build page

This support ticket is created 4 years ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 10 replies, has 2 voices.

Last updated by mikeH-4 4 years ago.

Assisted by: Shane.

Author
Posts
#1915053

I am trying to:Create a custome archive page

Link to a page where the issue can be seen:

I expected to see: I expect that (as per your videos documentation) when I click from Toolset Dashboard to create a new Archive page, it should open the page where I can define blocks (as per view etc)

Instead, I got: A page with a 'classic' text editor only containing these shortcodes: [wpv-filter-meta-html]
[wpv-layout-meta-html]

Something does not work. Could it be to do with caching again? I've cleared cache etc....

#1915189
archive-page-error.jpg

Attached is an image of the page that loads when I try to create an archive page.
I suspect it is something to do with server object cache (only because my previous two issues were).
But I have flushed server object cache and this has not fixed it.
Have tried several times over for different archives -- always the same issue 🙁

#1915241

Can you offer any insight here or help debug with my hosting provider -- wpmudev.org?
It could be to do with file permissions or something? Very frustrating not not be able to complete this relatively simple task...

#1915243

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Mike,

Thank you for getting in touch.

Based on what is happening here it seems that you may have a plugin that is disabling the gutenburg editor.

Unfortunately from your list of plugins I cannot tell which plugin is disabling the editor.

Can you temporarily disable all your non-toolset plugins and try again to see if the issues still remains ? You will need to delete your current archive and remake it.

Please try this and let me know the results and we can take it from there.

Thanks,
Shane

#1915245

I have tried disabling most and am running similar plugins locally without the issue.
I beleive it is a combination of Toolset and the hosting environment.
But I can't yet figure out what the specific issue is.

#1915257
broken-views-edit-screen.jpg

Does not appear to be a plugin conflict. Any other reason why this won't load? I have the same thing for previously created views -- when I go to edit them, they look like the attached screenshot. Perhpas there is something in there to help you debug???

#1915297

Tried disabling ALL plugins. Same issue persists. What do you suggest?

#1915329

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Mike,

As you say you are not experiencing the issue locally.

If you re-migrate that site thats working, does the issue persist when you migrate that local site to the live environment does the issue appear immediately or does it appear after you've made changes to the site.

Please let me know also if you can provide me with admin access please let me know.

Thanks,
Shane

#1915621

Any luck debugging? I need to go live with this site ASAP, but am currently blocked by this not working.
Please let me know. Thanks.

#1915653

I have finally found the issue:
In Toolset > Settings > Editing experience
This was set to: Show only the Blocks interface -- as you would expect for using the blocks interface...
BUT this was NOT being set.

It only works when I set to: "Show both the legacy and Blocks interface and let me choose which to use for each item I build"
Then set to "Use Block Editor" in the two settings below.
NB: also these two settings needed to be set twice as they did not save their settings first time round.

Frustrating but glad I have found the bug.
I note that unsetting and resetting did not reproduce the problem I was experiencing, so not sure how easy this is to recreate.
I can guarantee this was the issue though and is worth some investigation as was not an obvious fix.

Thanks

#1915655

See above