Rootside

I’m still getting this PHP notice when I disable my workaround.

Hi,

Just paste the code above into functions.php and see if it works.

If not, here’s advice on how to write your own little plugin: https://justintadlock.com/archives/2011/02/02/creating-a-custom-functions-plugin-for-end-users

Worth a try.

I know we’re not supposed to chat in these forums, but I’m happy to see that development has picked up again – I really like this plugin, and I hope these issues will be resolved.

Wild guess: do you mean the navigation menu?

On the admin screen for the menus, go to ‘Screen Options’ – you should find your taxonomies there. You can activate them and add taxonomy terms to your nav menu.

Are you using an emoji?

It’s a shot in the dark, but it sounds familiar, and I’m seeing a few similar threads here.
See https://www.ads-software.com/support/topic/no-tweets-available-mostly?replies=38

Would love to see a fix for this and I just noticed that the plugin was recently updated – sorry if this is not the problem you’re experiencing, ashton139 – but unfortunately the old thread is closed for new replies, even though it isn’t marked as resolved.

I’d like to add a tip – perhaps a topic marked as resolved is exactly the right place for it:

If you run into this error when adding theme support for title-tag, clear your browser cache before running the check.

Yes, you can – it looks like you switched on the debug mode on your site:

define('WP_DEBUG', true);

in wp-config.php

Just set it to false, and these notices won’t appear. You should only set it to true when you develop or test a site.

Ah, thanks.

I was hoping to be able to somehow hook into the shortcode function (or the shortcode’s callback function) and retrieve values from there – wouldn’t that be available globally?

Same here.

Another update, another bug.

Thanks for your help – however, I’ve switched to the Advanced Custom Fields plugin now (restricting metaboxes to certain areas is built right in).

They’ve come through now.

For 3.7.1, localised auto-updates are a few days behind apparently, so you might be affected if you’re running WordPress in another language, or even the British English version. More info on make.www.ads-software.com.

I couldn’t wait, and in wp-config.php, I changed
define('WPLANG', 'en_GB');
back to the default
define('WPLANG', '');
and the updates were there in the morning.

One more thing to note: I had to visit the sites, ie load any page, to trigger the email notification (they’re all test installs with no real traffic).

Same here. Tester plugin all green – but no updates, no emails, no other feedback. Just the usual update notification.

Hello again. Just chiming in to confirm that the issue still exists after the 2.6.0 update.

Aaron (the author), can you give us a quick shout with regards to a possible fix? Moondrop seems to have found something, but fiddling with source files is not really an option.

Feel free to contact me @rootside on Twitter about testing and/or access to my test install, but I think the problem is easily reproducible.

Thanks

Had the same problem on one particular website. This worked for me:

*/pagename

On other servers, just using the pagename without any slashes or placeholders usually works just fine – I suspect it has to do with the way your webhost sets things up: this problem occured on a cheap hosting package.

No support needed, thanks – you made changes in the plugin that broke the layout on a site, and now I have to adjust my CSS.

I’m sure those changes are for the better, and I agree that we have a certain responsibility to make sure that updates work with our code. I can also understand that not everything can be perfect, compliant and water-tight at the first try. But an update that changes things at the front end should at least be clearly labelled as such – with a warning in the changelog, or as a major update.

I know there was a major rewrite last year or so – that was clearly communicated and I could adjust everything before upgrading. Now, after a (apparently) minor update, things are messed up again. Makes me think I need to inspect every detail of this plugin every time there’s an update.