jglovier

Hey Deliverem,

In case you are still looking, here are a few articles that I just read through this evening responding to that very question. And James is right – it comes down to a matter of opinion.

Anyhow, you may wish to browse through these articles as they give some pretty detailed comparisons. Also, be sure to take note of the dates of the articles, as the content may or may not be up to date:

– https://perishablepress.com/wpseo-vs-aioseo/
– https://wpwidgets.net/all-in-one-seo-pack-vs-yoasts-wordpress-seo/
– https://wplift.com/yoast-wordpress-seo-vs-all-in-one-seo

Just installed the plugin today, also seeing the same issue with these Notices.

Thanks for the fix Jonathan. Hoping the plugin gets an update soon.

Hi cbee,

I just installed the Custom Permalinks plugin today too, and like you I see the PHP warnings. Technically, those are “Notices”, which is not an error. I’m not sure exactly what is causing the notice (could be an array which is look for a value in a key/value pair that does not exist…), but either way the notice won’t hurt anything.

Actually, what you can do in your wp-config.php file is to set WP_DEBUG to ‘false’) which you should not have set to ‘true’ for any site in production anyway) and the notices will no longer be displayed in the admin.

Alternatively, if you want to leave WP_DEBUG set to ‘true’ for a development environment, you can set WP_DEBUG_DISPLAY to ‘false’ in the file default-constants.php (as long as you have recently updated WP, otherwise this may still be located in wp-config.php or wp-settings.php).

Hope that helps.

Hah – yup. You’re right. Looks like I commented this plugin out a while back when I was having issues, and am actually using the twitter html widget currently.

Thanks.

Instead of the above query_posts parameters, try it like this (where the number 1 is however many posts you’d like to display:

<?php query_posts('showposts=1'); ?>

Yeah but that’s what I’m saying – it’s not asking for it that way. It’s still asking from the old URI format.

You can see right here (screenshot): https://cl.ly/KVCz or by going to joelglovier.com

I just got this issue on my local development environment I added a plugin folder called “gravityforms” to the plugin directory.

I tried deleting it, and when I did the message went away on page refresh. So I added it back into the plugins dir again to confirm, and sure enough the message appears on my dashboard again.

Why would a plugin directory trigger this message?

I tried running chmod -R 755 wp-content/plugins/gravityforms/ but that didn’t affect anything.

Suggestions?

Interesting. Yeah I’m running 2.4.0.

Screenshot: https://cl.ly/KU4p

Well – I found the answer. Turns out Twitter changed the API in March, and finally just shut off the old functionality at the beginning of October. (see this article)

Looks like the API URL must now use a new format that includes “api” as the subdomain, and “/1” after twitter, like so:
https://api.twitter.com/1/statuses/user_timeline/jglovier.json?callback=twitterCallback2&count=1

Apparently the Twitter for WordPress plugin users were discovering the same issue.

Can you please push a plugin update as soon as possible?

Thanks!!

To elaborate on esmi’s suggestion – you need to make sure the values for ‘DB_NAME’, ‘DB_USER’, and ‘DB_PASSWORD’ all correlate correctly to you is setup in MySQL on the host.

I’m also getting the no response from Twitter error (from the Jetpack version). I’m using WP 3.2.1.

Here’s another question – does this pluggin support adding the HTML5 placeholder attribute?

Awesome! That worked!! Thanks!

FYI – I am using another WP plugin on this page already called fmTuner – a last.fm plugin.

Except the way I’m running is with a php snippet that looks like this:
<?php if(function_exists('fmtuner')) { fmtuner(); } ?>

lol – yeah should have been more specific.

OK, the page is running within the WordPress loop – it’s a index file in a custom theme. But it’s not calling any posts, and it’s not set up as a page in WordPress. It’s static HTML.