hunter44

Thank you.

I followed these steps you wanted me to follow in your document https://yoast.com/help/how-can-i-uninstall-my-plugin/#database

However, it looks like I still have traces of Yoast items floating around. What are these and how do I get rid of them?

Database (Size)

yst_ga_top_pageviews (82,150)

yst_ga_source (18,530)

yst_ga_top_countries (7,407)

yst_ga_response (3,591)

The Yoast Uninstall instructions say that you’ll be prompted to delete the Yoast tables when you click “Delete” on the Plugins page. However, I was not prompted. Fortunately, I’ve figured out how to remove those tables using WP-Optimize.

Also, I don’t know how to search the database for those terms and delete them. Do they add to the overhead of loading my pages?

It would be awesome if you’d provide an Uninstall Yoast SEO plugin since the code and tables are so expansive. A lot of junior website developers like me have no idea how to access the database or make changes in it.

I see…You have to click Find & Replace in the dashboard sidebar and then click Replace in Database in the sidebar below that. Then, in the window that comes up, there is a Dry Run check box at the bottom.

Unfortunately, even though I purchased and installed the Pro version, I don’t see an option on that page to select the rule type “Advance Regular Expression (multiple lines at once / code blocks )“

That option is only available on the Real Time search/replace page which is not the kind of search/replace that I want to do…

• This reply was modified 7 months ago by hunter44.
• This reply was modified 7 months ago by hunter44.
• This reply was modified 7 months ago by hunter44.

Okay. So I need the Pro version for the rule to replace multiple lines of code, ie., “Advance Regular Expression (multiple lines at once / code blocks ). Also, it appears that I need the Pro Version to do a dry run. Is that correct?

I’m having the same problem. I added the magic 3 lines to wpconfig and WP_DEBUG now shows as ENABLED. Memory is already at 512M.

Anything else I can try?

Thinking it has to do with the length of the string being searched for and/or the length of the string being replaced, I did some tests.

I have about 560 replacements (one per page/post) of a string that is 177 characters, replacing it with a string that is 71 characters.

Thinking those strings were too long, I cut it down to replacing a string of 40 characters with one of 12 characters. That should be well within the limits of the plugin.

It still tells me to decrease the Max Page Size. So, maybe it’s incapable of handling 560 replacements in one shot???

Is it possible to break it down so it does just 100 replacements at a time?

Do you know how many characters is the max string for searching and the max for replacing, and do you know the max number of replacements for one search/replace query??

Apparently it’s a bug introduced in 4.6.1 by changes to the image file naming part of the code.

According to the release notes for 4.6.1 (https://www.ads-software.com/news/2016/09/wordpress-4-6-1-security-and-maintenance-release/):

“WordPress versions 4.6 and earlier are affected by two security issues: a cross-site scripting vulnerability via image filename, reported by SumOfPwn researcher Cengiz Han Sahin and a path traversal vulnerability in the upgrade package uploader, reported by Dominik Schilling from the WordPress security team.”

So, I guess in their effort to fix the “cross-site scripting vulnerability via image filenames,” they also changed the image titles to include the hyphens that are part of those filenames…

Anyone know how to report a bug to the WordPress team??

This appears to be a “feature” of WordPress 4.6.

I just upgraded and have the same problem. A real pain in the neck, as I’ll have to retype all my image titles every time I load a new image, and I load hundreds.

I have no idea why they would have changed it. Any insights from the designers would be helpful. Is it for SEO purposes???????

Argh!!

I tried both ways and it didn’t work either way. As noted above, the same is true for category id’s which are comma separated numbers. I think the OR functionality just quit all together.

THANK YOU!!!!!

Totally fixed!!

I really appreciate your help.

Thanks to the plugin developer for having all the old versions so handy.

Works like a charm. THANK YOU!!!

I love your plugin and rely on it 100% to create the navigation scheme I want on my website…

Here is a further clarification of the problem, and I didn’t describe it correctly above.

The problem is with using the “excludeposts=this” tag.

I have a lot of pages where I call LCP with the shortcode using that tag. I have always used it just like that, and the posts loaded fine.

Since doing the upgrade to 0.54.1, all my posts that have a call to the LCP shortcode with the “excludeposts=this” tag fail to load and give the fatal error stated above.

I have tried putting double quotes around the word “this” and I have tried single quotes and I have tried no quotes.

None of those things work.

The only workaround I’ve found is to remove the “excludeposts” tag from the shortcode call to LCP all together! I have done that on my most current posts.

I have not made that change to older posts because my hope is that this fatal error will be fixed soon. For an example of the failure, see:

https://roadslesstraveled.us/sun-valley-idaho-art-and-music/

My shortcode is this:

[catlist id=1,9,10,11,27,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,52,53,55,58,59,63,68,69,74,75,77,79,88 tags=sun-valley-area numberposts=20 link_target=”_blank” excerpt=yes excerpt_tag=span excerpt_class=lcp_excerptclass2 orderby=”date” order=”desc” date=yes dateformat=”m/d/y” date_tag=span date_class=lcp_dateclass2 template=”list-posts-home” excludeposts=”this”]

And again, I’ve tried it with and without single and double quotes, and the fatal error occurs in every case.

I am so confused. What do I need to do to fix the error? This is the 2nd time AdRotate has broken in 3 days.

Oh — I figured it out — You go into your Widgets and you’ll see your ID numbers are all blank. Replace the blank spaces with the correct AdRotate ID numbers.

I have not reverted back to the older version.

On Firefox and Chrome the problem appears to be fixed.

On Safari I am still getting the errors.

Same here – just updated and getting warnings on all the ads (not on the groups). Please fix!!

Warnings are for:

adrotate-output.php line 72
adrotate-cookie.php line 59