mccomb
Forum Replies Created
-
That seems to have fixed it. Thanks.
Forum: Plugins
In reply to: [Ultimate Nofollow] WordPress 4.2 issuesWhy does WP not give you a nofollow option? Seems like good SEO practice these days.
I am just using hand-coded nextgen links. They seem to work fine.
Never got it working – tried a few different things. I gave up and am working around it.
Forum: Plugins
In reply to: [W3 Total Cache] Blank (White) pages with W3 Total CacheRunning into the same problem here. Our pages with Gravity Forms routinely go white/blank.
Clearing the W3TC cache fixes the problem, but we cannot continue to monitor for this.Anyone have any luck with a fix?
@bermannyc – I’m having the same issue. It loads different images on different pages, but always the same image on the same page, so it is not randomly loading new ones on page refresh which is what I want it to do.
Anyone get that working?
This issue seems to be resolved with WordPress SEO in regards to the sitemap_index.xml file, but if you’re running Yoast’s Local SEO plugin, then there is a problem when try and load the location.kml file. The log file will fill up with the following:
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408
PHP message: PHP Warning: current() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 404
PHP message: PHP Warning: next() expects parameter 1 to be array, integer given in /public_html/wp-includes/plugin.php on line 408Verified this with Nextgen 2.0.30 and Yoast Local SEO 1.1.5,
Any ideas for a fix?
Same thing here. No idea why.
Just installed Nextgen 2.0.7 and now I have a conflict with the WP-Madrill plugin:
Mandrill: wp_mail has been declared by another process or plugin, so you won’t be able to use Mandrill until the problem is solved.
Any ideas on how to fix?
Forum: Plugins
In reply to: [Gravity Forms Salesforce Add-on] Why is the Salesforce password required?Really hoping for an answer here. It seems like a major security issue to me.
Anyone?
Forum: Plugins
In reply to: [Instapress] [Plugin: Instapress] Error when I try to activateOk, I found the solution to this: You need to change all the instances of “&$” to just “$”
In instagram.php:
Line 306: change &$nextMaxId to $nextMaxId
Line 309: change &$nextMaxId to $nextMaxId
Line 311: change &$nextMaxId to $nextMaxId
Line 777: change &$errorMessage to $errorMessageIn widget.php:
Line 80: change &$nextMaxId to $nextMaxId
Line 83: change &$nextMaxId to $nextMaxId
Line 85: change &$nextMaxId to $nextMaxIdHope that helps.
Forum: Plugins
In reply to: [Instapress] [Plugin: Instapress] Error when I try to activateSame error here:
Fatal error: Call-time pass-by-reference has been removed in /home/www/public_html/wp-content/plugins/instapress/instagram.php on line 306This happened after upgrading to PHP 5.4.4. The site actually gave me a 500 error and I had to disable the plugin to get the site back up. Now it cannot be re-enabled with this error.
Any update on a fix for the local.amazon.com issue?
I saw the new update and was hoping this was in there, but no luck!
yep, same thing here. Nothing is displaying.
Forum: Plugins
In reply to: [Instapress] Problem authorizing Instapress with InstagramThe fix is that you need to have your version of PHP compiled with SSL support. To do this, you need to add: “–with-openssl” and recompile.
You also need to make sure the line:
extension=php_openssl.dll
Is in your php.ini file.