Stringman

@displaywidget I do have to say that it is difficult to trust a plugin when an unknown developer buys out the original developer and adds mysterious geo-tracking functionality, violating WP security standards and getting the plugin taken down twice in the process. You could have avoided the rough start by releasing a simple update to the original plugin that added an informational message to the dashboard, educating your users about the change of ownership and coming geo-tracking functionality before releasing the major update. An option that could salvage your reputation at this point would be to concede the mistake and instead create a “professional” or “international” version of the plugin that contains the geo-tracking functionality (and other expanded features) and sell it directly from your own store, reverting the free version of this plugin to the original with some bug fixes. I think the community would appreciate that and it would restore some of your cred, especially since only a small % of your users care or even know about the geo-tracking feature and it reportedly adds a lot of bloat to the plugin itself.

My understanding is that updating to the latest version of the Slider Revolution plugin corrects the incompatibility with PHP 7. I haven’t tried it yet, but will let report back on what I find out after testing it. Another possible solution is to alter the plugin code so that it checks whether the function exists before calling it, as described here: https://premium.wpmudev.org/forums/topic/revolution-slider-network-activate-failed

Mustafa’s fix above worked for me. Core updates are working again.

line 149 of wp-admin/includes/file.php:

if ( empty( $filename ) || '.' == $filename ) {

replace with

if ( empty( $filename ) || '.' == $filename || '/' === $filename ) {

It’s been a while since I activated a fresh install of W3TC, but if the JavaScript minification is on, that would be the most likely cause of the problem.

Virtualsecretaries, the Smarter Analytics plugin isn’t designed to show analytics statistics within the WordPress back end. You have to log into your Google Analytics account to see the stats for each UA code you have setup and used. The strength of the plugin is that it allows for multiple UA codes to be used on a single wordpress site and that it lets you specify what code is used on a page by page basis. -Dave

This was in a different support thread for the same issue and it worked for me when I couldnt get anything but the default avatar to show:

<?php
global $current_user;
get_currentuserinfo();
echo get_wp_user_avatar($current_user->ID, 96);
?>

This was in a different support thread for the same issue and it worked for me when I couldnt get anything but the default avatar to show:
<?php
global $current_user;
get_currentuserinfo();
echo get_wp_user_avatar($current_user->ID, 96);
?>

Oh, and by the way. I think you might be misunderstanding the configuration. You can configure a single slideshow and put multiple instances of it throughout the site.

Not my plugin, but… The fact that it doesn’t work exactly how you want is not a valid reason for giving the plugin 1 star… that is just rude. You should reserve that rating for plugins that are poorly coded/supported, not those that simply don’t fit your specific design need. It would be much more courteous to give it 3 stars and suggest a more flexible design approach to the developer. Just my opinion.

You bet. Thanks again.

Cool. I’ll look for it. Until then, Yelp can stay turned off. That whole Yelp thing is a little bogus anyway…

I turned on debugging in the wp-config file and the output at the plugin location was: Fatal error: Cannot redeclare class OAuthException in /wp-content/plugins/display-tweets-php/includes/Twitter/twitteroauth/OAuth.php on line 8.

I went through and deactivated all of the other social plugins on the site that might be using Oauth and eventually found the conflict was with a plugin called Yelp It, which is used to display Yelp reviews. After disabling it, your plugin was fine. I turned on the other social plugins and everything remained stable. I don’t know if there is a way to define the class OAuthException with a different name to avoid the collision, but it seems like that would be the solution for the future.

Thanks for you help,

-Dave

I tested it on the 2012 theme and it works fine. The site I’m having problems with is using a child theme I created on the popular “Responsive” theme. All of the other widgets I install are working fine. I’m not sure what the problem is, but it does appear to be theme related. Any suggestions on how to find the problem within my theme that would cause this?

I love the time stamp on the tweets, and noticed it has a class on it. That is extremely helpful for styling the tweet output. I really like the way you set it up. I hope to use your plugin more in the future.

Thanks,

Dave

I went ahead and checked to make sure the same issue exists if using the php code implementation:

<?php if ( function_exists( “display_tweets” ) ) { display_tweets(); } ?>

The same issue occurs. Broken html output and no twitter feed. Thanks in advance, Dave

Further reading for you if needed: https://www.mydigitallife.info/php-scripts-open_basedir-restriction-in-effect-error/

Good luck!