Speeddymon

@reikiman I have to politely disagree. Your tone on here is the wrong King of tone. You’re using a free product for which they have no obligation to provide support.

You have already demonstrated you have at least some proficiency with PHP. Either fix it yourself in the (no longer supported) free version, or fork the free version into an open source GitHub project and start providing support for it yourself.

Either way, as someone who has no knowledge of PHP, I appreciate their product enough that I bought a license, so please kindly get off my thread if you’re going to bed rude.

Thanks for the update.

From what I recall in my testing (not home so can’t test for another couple of hours) there is a secure version of the image available by substituting https://, as when I use the WordPress plugin “SSL Insecure Content Fixer” it loads properly in https and I get the padlock. It just seems the canonicalizer module isn’t changing it by itself.

I’d like to not have to use an extra plugin to fix a single link, which was why I was hoping to see it fixed here. Lol

Thanks again for the FAQ link, I’ll check it out.

Hi Jeffrey,

I checked the Miscellaneous module based on your recommendation and enabled the option as recommended, however it is unfortunately still showing as the insecure link.

Is the pro version $29 one time, or is that recurring and how often is the recurring period?
I would like to see it fixed and am happy to spend $29 one time to get pro for life.

• This reply was modified 8 years, 4 months ago by Speeddymon. Reason: subscribe again

I’m not sure I understand your question. Install the plugin and the pings should appear automatically. If they don’t, then check that your chosen theme or some other plugin is not interfering.

And upgraded back to php 5.4. Somehow now the issue is resolved. No idea.

Update: Downgraded back to php 5.3. Issue persists. This must be something in the database somehow.

Side note: I have even gone so far as to make a complete backup of the directory my blog is installed in, delete the original directory, re-extract wordpress, and copy back ONLY my wp-config.php file. Still no change even after force-refreshing.

Here are screenshots to demonstrate what I am seeing..

The first is the working site:

https://postimg.org/image/4xshldkcn/

The second is the non-working site (notice the editor buttons are different and the DFW button is on the right end of the editor buttons instead of being it’s own separate button on the far right of the editor):

https://postimg.org/image/cc9qatved/

Well, I enabled logging of my php errors and was able to determine that the activation key wasn’t working for password reset because I had only GRANTed SELECT to my wordpress database user for the wordpress users and usermeta tables. So I changed that to all privileges, and was able to reset my password and get in. Now that I’m in, I’ll go back and re-enable plugins and make other changes necessary to get the site back online.

[redacted]

You’re probably right, but I haven’t seen any issues with it the way I put it though.

I placed the variable incorrectly in my previous post.

You can copy and paste this — replace line 285 as follows:

$commentdata = $wpdb->get_row($wpdb->prepare( “SELECT comment_ID, comment_parent FROM $wpdb->comments WHERE comment_agent = ‘Disqus/1.0:{%d}’ LIMIT 1”, $comment->id), ARRAY_A);

I just changed this on my own site, so we will see how it works.

I think you need to change

$commentdata = $wpdb->get_row($wpdb->prepare( "SELECT comment_ID, comment_parent FROM $wpdb->comments WHERE comment_agent = 'Disqus/1.0:{$comment->id}' LIMIT 1"), ARRAY_A);

to like this

$commentdata = $wpdb->get_row($wpdb->prepare( "SELECT comment_ID, comment_parent FROM $wpdb->comments WHERE comment_agent = 'Disqus/1.0:{%d}' LIMIT 1"), $comment->id, ARRAY_A);

So change the bottom line only — Disqua/1.0:{CHANGETHISHEREASDASHAHASDHA} and move $comment->id to just before ARRAY_A

I am testing it now on my site