Title: Rootside's Replies | WordPress.org

---

# Rootside

  [  ](https://wordpress.org/support/users/rootside/)

 *   [Profile](https://wordpress.org/support/users/rootside/)
 *   [Topics Started](https://wordpress.org/support/users/rootside/topics/)
 *   [Replies Created](https://wordpress.org/support/users/rootside/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/rootside/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/rootside/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/rootside/engagements/)
 *   [Favorites](https://wordpress.org/support/users/rootside/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 59 total)

1 [2](https://wordpress.org/support/users/rootside/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/rootside/replies/page/3/?output_format=md)
[4](https://wordpress.org/support/users/rootside/replies/page/4/?output_format=md)
[→](https://wordpress.org/support/users/rootside/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[GigPress] Undefined index: separator-gp – severe conflicts with other plugins](https://wordpress.org/support/topic/undefined-index-separator-gp-severe-conflicts-with-other-plugins/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [9 years ago](https://wordpress.org/support/topic/undefined-index-separator-gp-severe-conflicts-with-other-plugins/#post-9149734)
 * I’m still getting this PHP notice when I disable my workaround.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[GigPress] Undefined index: separator-gp – severe conflicts with other plugins](https://wordpress.org/support/topic/undefined-index-separator-gp-severe-conflicts-with-other-plugins/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [9 years, 6 months ago](https://wordpress.org/support/topic/undefined-index-separator-gp-severe-conflicts-with-other-plugins/#post-8435865)
 * 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: [http://justintadlock.com/archives/2011/02/02/creating-a-custom-functions-plugin-for-end-users](http://justintadlock.com/archives/2011/02/02/creating-a-custom-functions-plugin-for-end-users)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Twitter Widget Pro] no tweets available](https://wordpress.org/support/topic/no-tweets-available-5/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/no-tweets-available-5/#post-6314235)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Custom Post Type UI] Adding custom taxonomy to wp menu](https://wordpress.org/support/topic/adding-custom-taxonomy-to-wp-menu/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/adding-custom-taxonomy-to-wp-menu/#post-6262546)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Twitter Widget Pro] no tweets available](https://wordpress.org/support/topic/no-tweets-available-5/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [10 years, 10 months ago](https://wordpress.org/support/topic/no-tweets-available-5/#post-6313963)
 * 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://wordpress.org/support/topic/no-tweets-available-mostly?replies=38](https://wordpress.org/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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Theme Check] The wp_title() check conflicts with how _s handles title tags](https://wordpress.org/support/topic/the-wp_title-check-conflicts-with-how-_s-handles-title-tags/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/the-wp_title-check-conflicts-with-how-_s-handles-title-tags/#post-5578063)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[PHPEnkoder] Several PHP notices](https://wordpress.org/support/topic/several-php-notices-1/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [11 years, 3 months ago](https://wordpress.org/support/topic/several-php-notices-1/#post-5337695)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Awesome Weather Widget] Retrieving data from plugin](https://wordpress.org/support/topic/retrieving-data-from-plugin/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/retrieving-data-from-plugin/#post-4365869)
 * 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?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[The Events Calendar] 3.2 version seems to cause issue with Tag Pages](https://wordpress.org/support/topic/32-version-seems-to-cause-issue-with-tag-pages/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 6 months ago](https://wordpress.org/support/topic/32-version-seems-to-cause-issue-with-tag-pages/#post-4297429)
 * Same here.
 * Another update, another bug.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Multiple Post Thumbnails] Restrict MPT to a certain page](https://wordpress.org/support/topic/restrict-mpt-to-a-certain-page/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 7 months ago](https://wordpress.org/support/topic/restrict-mpt-to-a-certain-page/#post-4238826)
 * Thanks for your help – however, I’ve switched to the Advanced Custom Fields plugin
   now (restricting metaboxes to certain areas is built right in).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Not getting automtic updates](https://wordpress.org/support/topic/not-getting-automtic-updates/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 7 months ago](https://wordpress.org/support/topic/not-getting-automtic-updates/#post-4277300)
 * 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.wordpress.org](http://make.wordpress.org/core/2013/10/26/new-plugin-background-update-tester/#comment-11078).
 * 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).
 *   Forum: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Not getting automtic updates](https://wordpress.org/support/topic/not-getting-automtic-updates/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 7 months ago](https://wordpress.org/support/topic/not-getting-automtic-updates/#post-4277213)
 * Same here. Tester plugin all green – but no updates, no emails, no other feedback.
   Just the usual update notification.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Twitter Widget Pro] "No Tweets Available"… mostly](https://wordpress.org/support/topic/no-tweets-available-mostly/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 7 months ago](https://wordpress.org/support/topic/no-tweets-available-mostly/page/3/#post-3530869)
 * 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](https://wordpress.org/support/users/rootside/)
   on Twitter about testing and/or access to my test install, but I think the problem
   is easily reproducible.
 * Thanks
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Widget Context] [Plugin: Widget Context] Can't "target by URL"](https://wordpress.org/support/topic/plugin-widget-context-cant-target-by-url/)
 *  [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 9 months ago](https://wordpress.org/support/topic/plugin-widget-context-cant-target-by-url/page/2/#post-3082845)
 * 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.
 *   Forum: [Reviews](https://wordpress.org/support/forum/reviews/)
    In reply to:
   [[Testimonials Widget] Updates break layout](https://wordpress.org/support/topic/updates-break-layout/)
 *  Thread Starter [Rootside](https://wordpress.org/support/users/rootside/)
 * (@rootside)
 * [12 years, 11 months ago](https://wordpress.org/support/topic/updates-break-layout/#post-7774072)
 * 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.

Viewing 15 replies - 1 through 15 (of 59 total)

1 [2](https://wordpress.org/support/users/rootside/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/rootside/replies/page/3/?output_format=md)
[4](https://wordpress.org/support/users/rootside/replies/page/4/?output_format=md)
[→](https://wordpress.org/support/users/rootside/replies/page/2/?output_format=md)