lostpine

The update was successful, reads 3.2.2 and the site is correct. Thank you again for your prompt response to this issue.

Bob

Cockpit error. Was able to resolve the issue me.

For someone with cPanel access, it is a simple process to correct the beta issue that happened to me. The beta install gives you two plugins. The original plugin created a folder named “Top 10”. Installing a beta came through as “Top 10-1”. Beta 3.2.2 beta 2 did not influence the name of the folder. I deleted the “Top 10” plugin folder. It was deactivated at the time. I then renamed the “Top 10-1” to “Top 10”. Then went back to the website plugins and activated Top 10. Works fine.

Thank you for your help. If I can assist in the future with beta tests, let me know.

Bob

I have full cPanel access and can rename anything. However, the site is fine right now so I will wait until 3.2.2 is released then clean it up.

Bob

By the way, there are now two Plugins installed: the original 3.2 which I disabled, and the 3.2.2 active beta. Which plugin should I leave so the normal maintenance and updating updates the permanent change?

I did not install your beta 2 correctly. Now that I have, the changes you made are working correctly. The issue was that when I went to install the beta, it did not remove the original plugin. Therefore, it was not activated. I had to manually deactivate the old plugin and then reactivate the beta. The pages are displaying correctly. Sorry for the confusion.

Thanks for your help.

Bob

I am in the wigets screen. Did not check every option on the widget form but checked the TITLE at the top, it saved, checked the posts and pages boxes, but they did not save. Will be in and out this morning but will look for your messages.

I had a chance to experiment a little more. What I found is that I can change the title but both pages and posts checkboxes are not saved. Yet, on my dashboard, there is a box that shows me my top 1o correctly. I am in Florida so my day is ending. I will check back in the morning to see if there is more I can do.

Bob

I am more than happy to test beta software. Installed beta 2, activated the plugin, went to the widget, set the pages check box on, clicked update, and then closed the widget. Then went back and opened the widget and it is not checked. The site remains pointed to posts, not pages. Pages are not checked.

Bob

• This reply was modified 2 years, 5 months ago by lostpine.

I tried the resave but had no effect. When I open the “legacy widget” the check box for pages is not being saved. I set it, update, then open it again and it is unchecked. I also confirmed that I am using the legacy widget. All other data is correct. On my WordPress dashboard, I see the correct top ten pages. However, it does not translate to my widget.

I also totally agree. There are patterns of abuse and using a range of IPs is one of them. I miss the feature. There is also a missed feature. There are ISP companies that specialize on hosting hacking. The domain name is obviously also known in the look up. There should also be a direct option to “black list” all traffic from specific domains.

Blockquote goes white in dark mode, then text highlighted in blockquote also goes white making the blockquote unreadable.

Final note: While plugin Prevent XSS Vulnerability by Sami Ahmed Siddiqui is listed as having no known incompatibilities, the way it works is incompatible with PRINT MY BLOG. I deactivated it, reactivated the original plugin 2.9.8 and it worked perfectly with categories as a filter. FYI

I think this thread should be closed. Thank you for your efforts. The issue with how to prevent XSS and also not strip characters from a URL is a bigger issue than this thread should address.

Michael,

I had some time to look at the one plugin that is different between the sites I tested where PRINT MY BLOG worked and the large site it did not work on. This large site has had an issue in the past with XSS cross scripting hacking. I had added a plugin: Prevent XSS Vulnerability By Sami Ahmed Siddiqui to address the issue. This plugin specifically is removing the [] characters. While the plugin seems to have a lot of granularity in that I can deactivate the removal of any specific character, I don’t have sufficient background to understand if the characters [] are really necessary or an issue with XSS. Would love some advice if there is just a better way to address these things.

Did as directed with good results. No issues on the download and replacement. I went and ran the PRINT MY BLOG function without filters. Site produced a 3,318 page PDF file which I successfully saved to my computer. In looking at the PDF file, everything appeared to be as you would have expected it to be. Of course, I am interested in filtering at least on Categories. I don’t see much of a practical application for a PDF of my full site other than for archival purposes. The other sites that I tested PRINT MY BLOG are all hosted by GoDaddy. Actually, I have access to 8 sites because I volunteer to help not-for-profits with maintenance. Now that the holidays are past, I will start to look at plugins and see if I can find one that might be causing the issues you highlighted. When doing my original test, I kept the testing to lostpine as well as subwebs and did not use others under different accounts. In the next day or so, I should have more feedback. My first plugin to understand is one that I put in to Prevent XSS Vulnerability. This has been a problem for me in the past. I think this plugin does some of what you are concerned about.