Skip Navigation

[Resolved] using wpv-current-user info='logged_in' in conditional block revert to info='id'

This support ticket is created 2 years, 4 months 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

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

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 20 replies, has 2 voices.

Last updated by Luo Yang 2 years, 3 months ago.

Assisted by: Luo Yang.

Author
Posts
#2430295

it doesn't work in the blocks editor of widgets area (appearance > widgets )

debug option on conditional block -> doesn't output debug at all (if used by block in the widgets block editor)

there are issues regarding the Widgets block editor - but not in a regular post/page/content-template/custom-post/... block editors

please check using the footer widget area

with the generatepress theme - footer area widgets- block editor with toolset blocks: conditional block, fields & text block -

doest work as expected on this location only.

please help to reproduce because the theme dev say its a toolset plugin issue and not wp core (widgets new block editor) or the theme sidebar (footer widgets areas)

summery:

toolset blocks on widgets blocks editor doesn't work right (fields & text block doesn't work at all)

please help to check those issues

#2430305

should i open a new ticket about Toolset Blocks plugin issues on the new Admin Widgets blocks editor?

my client want to use the blocks editor, so i'm asking if Toolset Blocks plugin is not yet fully developed to work in the widgets block editor - and i should develop my own solutions for the widgets block editor.

or is it just a bug that the toolset developers should look into?

can toolset blocks 1.6.3 work with wp 6.0.1 widgets block editor (just as it works on regular blocks editor)?

#2430357

since there is an open known issue with Toolset Blocks plugin and the New Widgets Blocks editor, i've come up with a work around solution:

using a content template to wrap all content of widget area, using the blocks editor (working as expected for content template editing with blocks)

in widgets block editor add the toolset content template block with the newly created widget blocks wrapper template.

is this work around is ok performance wise,
what are the con's using a content template as a wrapper?

open issue link:
https://toolset.com/errata/toolset-blocks-do-not-work-in-new-block-based-widgets-editor/

#2430805

For the new questions:
Q1) is this work around is ok performance wise,
As you can see, in the plugin description of "Classic Widgets":
https://wordpress.org/plugins/classic-widgets/
Classic Widgets is an official plugin maintained by the WordPress team that restores the previous (“classic”) WordPress widgets settings screens. It will be supported and maintained until at least 2022, or as long as is necessary.
So I think it is wise to use this plugin.

Q2) what are the con's using a content template as a wrapper?
What is the "con's" are we talking about?
Please elaborate the question with more details?
How and where do you want to use "content template as a wrapper"?

#2437553

- How and where do you want to use "content template as a wrapper"?
inside a widget, using the WBE (Widgets Block Editor) for footer and header widgets areas.

since there are some issues with several toolset blocks in the WBE ->
i create a content template block for each widget area,
and use the content template Block Editor ( works with all blocks) to insert toolset blocks properly to each one of the Content temp'.
this way my client can still interact and control the widgets areas with the Blocks UI.

is this description explained my use case and question?

#2437903

According to our support policy, we prefer one ticket one questions. For other new issues, please check the new thread here:
https://toolset.com/forums/topic/in-widgets-block-editor-add-the-toolset-content-template-block-with-the-newly-created-widget-blocks-wrapper-template/