Alex

Hello,

As a pro user, you have access to our private technical support system. I’ll close this duplicate request to prevent confusion.

PS: We fixed this issue in version?3.3.13

Regards,
Alex

Hello,

We fixed this issue in version?3.3.13. Please update to the latest version and let us know if the problem is resolved.

Regards,
Alex

Hello,

I recorded a video showing how to I try reproduce the problem: https://shot.nkdev.info/Bvv3yL11FkSJtVdCj4fy

The main pages and posts worked correctly. The only issue occurred with the portfolio archives. By adjusting the permalink settings, this problem was resolved. While I’m not familiar with the specific plugin and theme settings, their default configurations work well together without conflicts.

I also checked the Kadence Blocks plugin, and it works correctly: https://shot.nkdev.info/8vqM9LhVVGSJJ92pdJQD

PS: If the problem persists, contact our technical support team through the private system. We will carefully review and address your issue: https://nk.ticksy.com/

When creating a request, just choose “Bug Report”

Regards,
Alex

• This reply was modified 4 days, 18 hours ago by Alex.
• This reply was modified 4 days, 18 hours ago by Alex.
• This reply was modified 4 days, 18 hours ago by Alex.

Hello,

Please move the tt-anchor property from the content control to the inspector to fix the block rendering error. This known issue occurs when the URL control is present in the content: https://www.ads-software.com/support/topic/error-this-block-has-caused-an-error-and-cannot-be-previewed/

Regards,
Alex

Hello,

Unfortunately, this feature is not currently available in the plugin.

Regards,
Alex

Hello,

I tested several plugins that worked well (almost all popular plugins). However, I disliked that they only offered shortcodes and lacked a block system.

Regards,
Alex

Hello,

Please read this thread and my colleague’s conclusion at the end: https://github.com/nk-crew/lazy-blocks/issues/296#issuecomment-2012043228

“Since the iframe editor was introduced in Gutenberg, some components have stopped working correctly inside the content. Initially, inserting input fields inside the block content was not in the Gutenberg paradigm, but we decided to make it possible. I think we have to use controls in the Inspector and stop using them in content. We should also add the possibility of using the RichText component (https://developer.www.ads-software.com/block-editor/reference-guides/richtext/), which is Gutenberg’s preferred method to edit elements in the block output directly.”

You can also read this threads:

• https://github.com/nk-crew/lazy-blocks/issues/308
• https://www.ads-software.com/support/topic/problem-changing-url/

We plan to implement stricter limitations on URL field insertions in block content, unless Gutenberg resolves this issue first. Currently, we cannot influence WordPress editor development since we are not Gutenberg’s core contributors.

I have marked the issue as resolved. We have fully investigated the problem and documented it in our issue tracker.

PS: If Gutenberg makes any progress, we can reopen and revisit this issue. However, currently there are no signs of advancement.

Regards,
Alex

• This reply was modified 1 month, 2 weeks ago by Alex.
• This reply was modified 1 month, 2 weeks ago by Alex.

Hello,

I recorded a demo video showing how to set permissions with the PublishPress Capabilities plugin for block usage in the post editor: https://shot.nkdev.info/w8yvlrb5yc0jQYcrr3jh
The video confirms that the permissions match exactly what you specified, and they function correctly.

If you’re experiencing issues, the permissions may not have properly applied to your role group or user. Try resetting the permalinks and server settings to their defaults. There might also be conflicts with other plugins, but I would need more information to identify the specific cause.

Regards,
Alex

Hello,

Child and parent categories appear in the same order, and nested categories are not currently supported. If you have development experience, you can customize the category display style by modifying the template. Learn how to do this at: https://visualportfolio.co/docs/developers/changing-default-templates-and-styles/

Regards,
Alex

Hello,

I’ve created a future task to evaluate this integration. We’ll discuss it with colleagues to determine if it’s necessary. While I can’t guarantee whether we’ll implement this support, if approved, it won’t be available soon.

Regards,
Alex

Hello,

I checked but couldn’t reproduce the error. The issue might occur if you’re placing the URL Control inside the content: https://shot.nkdev.info/Y8NLYYl6tT4J9444QKmB
This will cause a rendering error and crash the block. This is a known issue that affects new themes but not older ones. It’s related to the Gutenberg editor frame’s functionality and appears in various situations. While we attempted to restrict control selection through the interface, we likely didn’t add enough conditions to block this field properly.

If you encounter this error, try moving the URL Control to the inspector. Plugins and themes can disable Gutenberg’s features and let you skip it, but this approach may cause problems and is not recommended.

PS: If you encounter an error caused by other factors, please export the problematic block to me for testing in my system. You can find export instructions here: https://www.lazyblocks.com/docs/export-blocks/

Regards,
Alex

Hello,

Human-friendly URLs are currently only available for archives. For more information, visit:
https://visualportfolio.co/docs/portfolio-archive/
https://visualportfolio.co/docs/settings/permalinks/#portfolio-archive-permalink

We may add custom link editing when we implement the separation of blocks into filters and main content. For now, you can only modify links by customizing the project code yourself.

Regards,
Alex

Hello,

Thank you for reporting this bug. I’ve confirmed and reproduced the issue on my system. We’ll include a fix in the upcoming update.

Regards,
Alex

Hello,

When you open the inspector, you can see a JavaScript error related to the isotope extension. This error occurs because another plugin or theme is also loading isotope. You can view the error here: https://shot.nkdev.info/lfZn9dD0HtpxTkspkQ1M

Here are the steps to follow:

• Disable plugins one at a time to identify which one conflicts with the gallery.
• Change the theme to a default option like Twenty Twenty-Five
• Disable all caching plugins during testing to see errors change in real time.
• Please specify which plugin conflicts with the gallery so I can investigate the issue.

Regards,
Alex

Hello,

This bug was fixed 2 months ago in version 3.3.10. The release is available. Here is the list of changes: https://www.ads-software.com/plugins/visual-portfolio/#developers

Regards,
Alex

• This reply was modified 3 months, 2 weeks ago by Alex.