microberto

@shazahm1hotmailcom – Please allow me to add a “me too” to this. I am willing to donate. I use the classic editor (cleaner HTML) and would like to place a [toc] slightly lower in the page — a few paragraphs below my first couple of headings.

Right now the options are too inflexible and a shortcode’s placement should have precedence over the default. There are many cases when I want to manually create a table of contents below some of the introductory headings on large posts.

Thanks!

Change the publish dates for the individual posts on your WordPress site. Then give Apple Podcasts 24 hours to update the information on your show’s public listing there.

It would be nice to be able to set the date manually without messing with the blog post date.

Reason being, if we want to update the blog post and give it a newer date (to bump the updated information to the top of the blog for our readers), that’d mess up the date on the Podcast feeds too, which could throw off iTunes / Google Play / etc.

Can we get a feature request to get a manual date / timestamp in the “Podcast Episode” section?

Thanks!

RSS feeds to not paginate, that is a limitation of the RSS spec.

Thanks, I can’t argue with that, although it’s odd that WordPress *sometimes* accepts the paged parameter for it.

Would you mind explaining why you want your RSS feed to paginate? Perhaps we can find an alternative for you.

We are actually trying to pull tag/date/URL data from our blog into our main site and database. I thought the RSS would be available for use, but since it’s not, I’ll need to find a secure API plugin to retrieve the data from the blog.

Another solution is to switch to the default permalink mode (which will allow us to use paged RSS) and then use the Custom Permalinks plugin so our permalinks stay the same.

But if this is not part of the RSS spec, using an API plugin is probably best long-term.

Thanks for the response!

Same deal here. Looks like Google Maps needs an API key now. I had to hardcode it into the plugin, which stinks.

Interestingly, this worked fine for me when running locally on lvh.me (localhost).

• This reply was modified 8 years, 2 months ago by microberto.

Got it – had to reinstall php7.0-curl!! My mistake, closing this out. Thanks for your time!

Hey Daniel, thanks for testing it!

What repository are you using for PHP7.0?

I’m using this one:
https://launchpad.net/~ondrej/+archive/ubuntu/php

I can replicate this issue on every Ubuntu LTS 14.04.5LTS machine. Here’s my packages installed:

$ apt list --installed | grep -i php

php-common/trusty,now 1:43+deb.sury.org~trusty+1 all [installed,automatic]
php-imagick/trusty,now 3.4.2-2+donate.sury.org~trusty+1 amd64 [installed]
php-pear/trusty,now 1:1.10.1+submodules+notgz-8+donate.sury.org~trusty+2 all [installed]
php7.0/trusty,now 7.0.9-1+deb.sury.org~trusty+1 all [installed]
php7.0-cli/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-common/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-fpm/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-json/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-mysql/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-opcache/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-readline/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]
php7.0-xml/trusty,now 7.0.9-1+deb.sury.org~trusty+1 amd64 [installed]

No clue what’s wrong, but interestingly, this is *not* happening on an Ubuntu 12.04.5 LTS machine!

Any ideas, or more ways I can help debug? I hate not having backups going!!

Thanks again!

Got a few critical bugs to look at:

https://www.ads-software.com/support/topic/site-blank-after-update-to-wordfence-619

https://www.ads-software.com/support/topic/wfwafstoragefileexception

Same issue here, happened on two sites when using WordPress 4.5.3.

PHP message: PHP Fatal error:  Uncaught exception 'wfWAFStorageFileException' with message 'Unable to open /home/mysitedir/public_html/wp-content/wflogs/ips.php for reading and writing.' in /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:355
Stack trace:
#0 /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(452): wfWAFStorageFile->open()
#1 /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(409): wfWAFStorageFile->fetchConfigData()
#2 /home/mysitedir/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(729): wfWAFStorageFile->getConfig('wafStatus')
#3 [internal function]: wordfence::enqueueAJAXWatcher('index.php')
#4 /home/mysitedir/public_html/wp-includes/plugin.php(525): call_user_func_array('wordfence::enqu...', Array)
#5 /home/mysitedir/public_html/wp-admin/admin-header.php(92): do_action('admin_enqueue_s...', 'index.php')
#6" while reading response header from upstream, client: 108.162.221.117, server: www.mysite.com, request: "GET /wp-admin/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "www.mysite.com"
2016/06/22 07:33:15 [error] 3232#0: *85 FastCGI sent in stderr: "PHP message: Unable to open /home/mysitedir/public_html/wp-content/wflogs/ips.php for reading and writing.
PHP message: Unable to open /home/mysitedir/public_html/wp-content/wflogs/ips.php for reading and writing.
PHP message: PHP Fatal error:  Uncaught exception 'wfWAFStorageFileException' with message 'Unable to open /home/mysitedir/public_html/wp-content/wflogs/ips.php for reading and writing.' in /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:355
Stack trace:
#0 /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(452): wfWAFStorageFile->open()
#1 /home/mysitedir/public_html/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(409): wfWAFStorageFile->fetchConfigData()
#2 /home/mysitedir/public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(729): wfWAFStorageFile->getConfig('wafStatus')
#3 [internal function]: wordfence::enqueueAJAXWatcher('index.php')
#4 /home/mysitedir/public_html/wp-includes/plugin.php(525): call_user_func_array('wordfence::enqu...', Array)
#5 /home/mysitedir/public_html/wp-admin/admin-header.php(92): do_action('admin_enqueue_s...', 'index.php')

Using PHP5.5-FPM that came with this: PHP 5.5.36-4+deb.sury.org~precise+1 (cli)

Try removing Wordfence and table data and then do a clean install again. That will recreate all of the database tables with the correct permissions.

-Brian

Actually simply deactivating / deleting / re-installing / activating the plugin worked! After activating, the firewall was enabled and seems to be working. This will definitely help on this site…

Thank you!

Hi, thanks for the quick response.

Absolutely nothing is happening in the console. Other settings (such as the email address for alerts) save. This checkbox doesn’t though!

Same behavior in both Firefox and Chrome.

Is there a way to enable it in the database?

Thank you!

Same!

Not sure if it’s WP 4.3.1 or Redirection 2.4.1.

Going to try Redirection 2.4.0 with WP 4.3.1 and see:

OK, in WP 4.3.1 and Redirection 2.4.0, when entering my Source URL, the Target URL field simply disappears!

Not sure what WP did here, but a few things are going wrong here.

The good news is that if you do the following, you’ll be okay:

1. Put your target URL in first.
2. Put your source URL in (the target URL will disappear).
3. Submit (you’ll get the weird JSON here)
4. Go back and refresh your /wp-admin/tools.php?page=redirection.php page

All seems to work.

Wow, thank you so much!

What’s frustrating is that with Ubuntu 12.04LTS, the versions of CURL are stuck at 7.22. Can’t even find a trustworthy repository with 7.39+ right now.

If I can’t get a backport, may need to update this server at some point. I don’t like installing thing from sources because I’d forget about it and not check for security updates.

Thanks again!

Hi Daniel, thanks for the help a bit ago.

I installed and activated that plugin, but still get this error:

The HTTP response test get an error "error:14077438:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert internal error"

I tried restarting PHP and nginx to see if that’d help.

Something else going on here?

The setup remains the same – Nginx server + CloudFlare FULL SSL. The certificate on the nginx server is self-signed, which is permissible by CloudFlare. The ciphers remain the same as above.

Thanks a ton!

As an FYI, here’s my nginx SSL setup on this one:

ssl_session_cache shared:SSL:50m;
        ssl_session_timeout  5m;
        ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;

        ssl_ciphers 'EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH+aRSA+RC4 EECDH RSA+AESGCM RSA+AES !RC4 !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !SRP !DSS';

        ssl_prefer_server_ciphers on

Got that from somewhere on GitHub as a quality secure version.

Nice, I’m still having this issue with Custom Permalinks, can the fix get patched in?

It’s not really “resolved” as the fix will disappear every time we upgrade.