John

Many thanks!

Thanks for this, problem solved.

In my case, the culprit was DX Delete Attached Media.

I’ll try to inform them about that.

More info about this vulnerability here:

https://patchstack.com/database/vulnerability/email-posts-to-subscribers/wordpress-email-posts-to-subscribers-plugin-6-2-sql-injection?_a_id=431

Waiting for a patch, with thanks.

Looks good then, many thanks.

Thanks @bretmiller

Many thanks, that works fine again now.

OK thanks, it works but I also see that I need to create the shortcode before, the same way we do for PDFs but your documentation gives wrong instructions here: https://embedpress.com/docs/embed-facebook-posts-wordpress/

I also realize that the embed of PFB posts only includes the FB summary and not the full post. Is there a way to get the full FB post (without “see more…”)

Hello, I did follow-up by email about this question at that time and got a reply that you were testing but I don’t have any updates since some time and nobody replies to my messages anymore.

Thanks for this, I understand.

No, there is no other .htaccess but this one has also some snippets from WP Fastest Cache like this one:

RewriteEngine On
RewriteBase /
RewriteCond %{HTTPS} =on
RewriteCond %{HTTP_HOST} ^mydomain.com

But I think I prefer leave things as they are now because everything works fine and I don’t it would be useful to investigate further about the 301 redirection in .htaccess.

You should rather maybe add something about subdirectories in your plugin’s FAQ.

Thanks for your help!

Thanks, but please clarify because I’m lost here.

• what precisely is NOT supported, what is “this”?
• what is a “constant” and to what are you referring precisely please?
• when reading this updated page, I understand that I first have to add a “define” line and then remove it again? But, for me, the .htaccess is now OK (after changing the settings to PHP), so what should I do, just remove the previous “define” line in wp-config.php?
  
  Thanks.

… already done my friend!

Thanks, but I just found out that this snippet generated by Really Simple SSL is the culprit! I followed their instructions on how to remove their .htaccess snippet (that I previously had enabled) and the problem is solved.

I just removed this snippet but I’ll send you an email anyhow. Thanks.

Other than your own sections, I only found this one, created by Really Simple SSL:

RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteCond %{REQUEST_URI} !wp-content\/cache\/(all|wpfc-mobile-cache) RewriteCond %{REQUEST_URI} !^/.well-known/acme-challenge/
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]

No problem, you are welcome!

I tried but no change. Let’s see if it persists after a couple of weeks and if other people have the same issue.

Tested with Chrome and FF.