[Escalated to 2nd Tier] Single quotes in URI causing problems

[Author]

Posts

[mikeF-2]

Hi Toolset,

I'm having problems with my webhost blacklisting my IP due to bad URI requests due to single quotes in the URI.

Here's an example:

/wp-admin/[tb-dynamic%20provider='__current_post'%20post='current'%20source='media-featured-image-data'%20force-string='first'%20]

Is there a workaround? Thanks in advance.

[Luo Yang]

Hello,

Please elaborate the question with more details, describe detail steps to duplicate the same problem.

How do you setup the custom field? is it a custom image field created with Types plugin?
How do you display above custom field or links?

I need to test and debug it in my localhost, thanks

[mikeF-2]

Hi Toolset,

I'd love to provide more specific information for you to try to recreate the problem, however, I haven't figured out what or where the single quote URI problem happens, other than it only occurs on the wp-admin backend.

I haven't dug deeply to know what tb-dynamic does, so I'm not entirely sure what details to provide so you can try to replicate. tb-dynamic seems to be used in toolset-blocks, toolset-maps, and wp-views. (I'm not using Cred on this site yet, but will be shortly.)

Briefly, I'm using Toolset to make a membership site and business directory. I'm using the new Views Blocks, although I did temporarily switched to Views as a workaround to see if I could show a search bar separate from the search results. (You can't, so I switched back to Views Blocks)

I have 2 custom post types, each with their own group of custom fields and content templates,

Looking at the bad URI example given earlier, I thought I'd look into the featured image URLs for one of the custom posts.

I used WP ALL IMPORT to batch import data into my magazine custom post. The featured image was a mix of text and column data. (See attached image)

If I check the featured image information of the custom post in the database, however, the URL of the featured image seems okay and I don't see anything out of the ordinary. (See attached image.)

At the time of the error, I was using Toolset Blocks v1.0.2 and have now updated to Blocks v1.1.1 (and Views v3.1.1)

Can you give me a clue where Toolset be creating a bad URI request on the wp-admin backend? Alternatively, can I give you admin access so you can get the specific information you need to try to replicate the error? Thanks for your help.

[mikeF-2]

Hi Toolset,

It looks like the bad URI is coming from a toolset image block used in a view loop. (image attached)

When I remove the block, the error in the console goes away.

The block is set to dynamic image source > current post > featured image data

It looks like it's giving a 404 error, but the featured image actually loads fine in the view loop editor, as well as the back end and front end. (Greyed out for privacy.)

FYI I did use WP ALL IMPORT to upload the custom posts. In this case, I set it to load a specific image URL already in the media library as the featured image. When I check the custom post in the business directory, the featured image seems to load fine.

Any ideas why the toolset image block is causing errors with a dynamic image source > featured image data?

Thanks for your help.

[Luo Yang]

Please try these:
1) Make sure you are using the latest version of Toolset plugins, you can download them here:
https://toolset.com/account/downloads/

2) In case it is a compatibility problem, please deactivate all other plugins, and switch to wordpress default theme 2020, deactivate all custom PHP/JS code snippets, and test again

3) Create a new post with feature image manually(without WP ALL IMPORT plugin), test again.

4) If the problem is fixed, then it should be a problem when you use WP ALL IMPORT plugin to import the data.

5) If the problem still persists, please provide a database dump file of your website in below private message box, also point out the problem post URL, I need to test and debug it in my localhost. Thanks
https://toolset.com/faq/provide-supporters-copy-site/

[mikeF-2]

Hi Toolset,

I've narrowed down the problem to a conflict with the Toolset image block used in a view loop and Yoast SEO (v13.0)

/wp-admin/[tb-dynamic%20provider='__current_post'%20post='current'%20source='media-featured-image-data'%20force-string='first'%20]

I realize that support for other plugins is not your responsibility, however, before I begin a fun conversation where everyone says it's the other plugin's problem, do you have any ideas what might be the root of this problem?

On this specific page which is a business directory listing, I am calling other dynamic content with Toolset that doesn't seem to be conflicting with Yoast. Is there anything unique to the Toolset Image Block?

Thanks for your help.

(To answer your questions above,

1) I am now using the latest versions of Toolset)

2) When I deactivate all other plugins and use wordpress default theme 2020, there are no bad URI errors. The plugin causing the conflict is Yoast SEO (v13.0)

3) When I create a new post with the feature image manually (without WP ALL IMPORT plugin) I still get the same bad URI errors (with all of my plugins activated, including Yoast SEO.)

4) The problem is not with ALL Import. There are no bad URI errors if Yoast SEO is turned off. )

[Luo Yang]

I assume we are talking about the plugin "Yoast SEO", download from:
https://wordpress.org/plugins/wordpress-seo/

I have tried it in my localhost, but can not see the same problem as you mentioned above, please provide the database dump file of your website in below private message box, I need to test and debug it in my localhost, thanks

[Luo Yang]

Thanks for the details, I am downloading the file, will update here if there is anything found

[Luo Yang]

I can install your database dump file, where can I see the problem you mentioned above?
On this specific page which is a business directory listing
Please point out the problem page URL, thanks

[mikeF-2]

Sorry, I missed your second response. Here is the problem page url. The problem only happens on the wp-admin backend.

/wp-admin/post.php?post=7542&action=edit&lang=en

Thanks for your continued help.

[mikeF-2]

Just wanted to add that I used Kadence Blocks in the design of the search layout in that post /wp-admin/post.php?post=7542&action=edit&lang=en , but I don't believe that's the problem.

If you turn off the search in that view (to get rid of the kadence blocks code on the page), I believe you'll see the toolset image block loading the dynamic featured image from the business directory listings still triggers errors when Yoast SEO is activated.

Console screenshot attached. Any insight you can find is appreciated.

[mikeF-2]

One more follow up note. I am able to replicate this conflict between the Toolset Image block and Yoast SEO on a brand new WordPress install on my webhost:

• Created a fresh wordpress install (5.3.2) with the latest Toolset plugins (Blocks v1.1.1; Types 3.3.10) using the default Twenty Twenty theme.
• Created a custom post type with no custom fields
• Created a test custom post with a featured image
• Created a page with a toolset view block and no search.
• Added toolset single field block with dynamic text: standard field; post source - current post; source - post title with a link
• Added toolset image block with dynamic image source: post source - current post; source - featured image data
• There are no errors in the console. (see attachment)
• Activate Yoast SEO (13.1)
• Refresh page with the toolset view block and now there are multiple errors in the console. (See attachment.)
• Getting 404 errors trying to load

  /wp-admin/[tb-dynamic%20provider='__current_post'%20post='current'%20source='media-featured-image-data'%20force-string='first'%20]

When you tried to recreate the issue on your local host earlier at comment 1512271, did we use a similar process?
https://toolset.com/forums/topic/single-quotes-in-uri-causing-problems/#post-1512271

Thanks for your help!

[Minesh]

Luo is on holiday today. He will get in touch with you tomorrow as soon as you will back to work.

[mikeF-2]

No worries! Thanks for the update.

[Luo Yang]

Thanks for the details, I can duplicate the same problem in my localhost with the steps you provided above, I have escalated this issue, will update here if there is any news.