Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter Windpipe the Clown

    (@ravenseye)

    On my test sites I’m able to leave comments just fine by checking the box. Thanks for checking!

    Forum: Plugins
    In reply to: [Adminimize] Errors

    I reset the settings, deactivated and deleted from WP admin, then downloaded a fresh copy from the Repo and installed by uploading via FTP. These notices persist. Any other suggested solutions?

    @jason Yes, I just tried replacing a few strings in google-analyticator.php with data from my own Google API and of course everything crashed and burned, so I can see that it’s not as simple as that. And, my accounts are already back up and working now that I restored the plugin to its original state.

    Thanks so much for all your hard work on this!

    Is it really necessary for the plugin to use the Google API attached to the plugin’s Google account? Isn’t it possible to allow a user to get our API key from Google, then enter that into the plugin and have Google track API calls for each of us? This would eliminate the strain on the plugin’s Google API account.

    It seems that this problem will continue to plague us indefinitely if all that happens is an increase in the call limit from Google for the plugin’s account, since this seems to be the only functional GA plugin and worldwide use of WP is constantly on the rise.

    Perhaps you could allow this as an option for developers using your plugin? How hard is it to get a Google API key for this sort of thing?

    I’ve got this error too, on all my sites. And none of these are high traffic sites. I don’t understand exactly what this means, and visits to Google Forum posts about the API are over my head. But I get the exact same error message as posted by Jason in all my Dashboard widgets on several accounts.

    I do have 40-60 properties in my Analytics account, but again even with all of these sites combined the traffic is not high by any measure.

    Thanks for the tip, Rastarr. I just successfully authenticated using Chrome on OS X too. In case it helps the devs, here’s the error message that fills the Dashboard widget window in Firefox (current version, OS X):

    Fatal error: Uncaught exception ‘Google_AuthException’ with message ‘Error fetching OAuth2 access token, message: ‘invalid_grant” in /home/website/public_html/wp-content/plugins/google-analyticator/google-api-php-client/src/auth/Google_OAuth2.php:113 Stack trace: #0 /home/website/public_html/wp-content/plugins/google-analyticator/google-api-php-client/src/Google_Client.php(131): Google_OAuth2->authenticate(Array, ‘…’) #1 /home/website/public_html/wp-content/plugins/google-analyticator/class.analytics.stats.php(68): Google_Client->authenticate(‘…’) #2 /home/website/public_html/wp-content/plugins/google-analyticator/google-analytics-summary-widget.php(188): GoogleAnalyticsStats->checkLogin() #3 /home/website/public_html/wp-content/plugins/google-analyticator/google-analytics-summary-widget.php(104): GoogleAnalyticsSummary->getAnalyticsAccount() #4 [internal function]: GoogleAnalyticsSummary->ajaxWidget(”) #5 /home/website/public_html/wp-includes/plugin.php(403): call_user_func_array in /home/website/public_html/wp-content/plugins/google-analyticator/google-api-php-client/src/auth/Google_OAuth2.php on line 113

    I just updated to 6.3.1, and I get a blank white screen after clicking the Click HERE link, too. I uninstalled the plugin, reinstalled fresh, but it’s still broken. Can’t authenticate. It looks like 6.3.1 did not fix the issue.

    Thread Starter Windpipe the Clown

    (@ravenseye)

    Okay, after exhaustive debugging I found that the problem was some sort of conflict with the plugin WP Better Emails. I tried my customized Visual Editor in a clean installation as Editor, and it worked fine, so then I started systematically turning off plugins until I found one that, when removed, resulted in my problem going away. Fortunately, this plugin was not very important to me.

    Hopefully this post will be helpful to anyone out there who runs into the same conflict.

    Hi JJCoder,

    Thank you! I had just used “featured” when I hacked your plugin to fix the validation, which lacks specific meaning even more than the “nivo slider image” alt text in place now.

    I could not figure out how to actually pull alt text from each NextGen image, but I think that even this unspecific alt text is better than none — not only for validation but for folks using screen readers and other non-graphic devices as well.

    Now I won’t have to hack your plugin to make it validate as I continue to enjoy using and updating it on into the future… awesome!

    Thanks JJ for fixing the navigation for WP 3.2! It works great…

    kenelysergio, I haven’t tried this plugin with captions, so I don’t know if that would work on my installations.

    JJ, the plugin now works great for my purposes except for that it produces invalid code in HTML5 and XHTML Strict by adding a <border> element to each image and lacking an <alt> element. Borders are deprecated in HTML and alt text is required by modern standards.

    I found it easy to hack a single line of code in your plugin to correct this problem, but it might be good if you could incorporate this little fix in your next update. A lot of WP developers are concerned with validating at least as much as possible these days, and fixing this could grow your user base. This is not a WP 3.2 issue per se, and I’ve posted about this in more detail in the Plugins section, but I thought I’d mention it since I’ve seen no response over there.

    Thread Starter Windpipe the Clown

    (@ravenseye)

    I just realized that this post belongs in the Plugins and Hacks section of the WP Forums. Mod, please feel free to move it if you like. I’m still a bit of a noob with posting here.

    Before today’s update, I had hacked the plugin by simply adding the current version of jquery.nivo.slider.pack.js (v 2.6) from the Nivo Slider website. Earlier versions of Nivo Slider were incompatible with JQuery 1.6.1, which WordPress uses now as of version 3.2.

    My hack of this plugin worked fine, having only replaced the .js file, but when I tried to replace the stylesheet with the Nivo Slider 2.6 version stylesheet, things broke.

    This update does appear to fix things, except I’m experiencing the same navigation glitch described above: the navigation arrows show up on the first image (on hover), but disappear and never appear again on succeeding images. The bottom navigation is present and works fine.

    Dev, do you think you might be able to update this? I love this plugin… I’d been wanting to integrate a slider with NGGallery for months, and had just started writing my own plugin to do this much less elegantly when you released this great plugin and saved me the trouble.

    I’m setting up a testing server on Snow Leopard now, using MAMP Pro and WP 3.0 with multiple site functionality. I’d love to be able to auto-update plugins and WP software on my local machine, but I have not been able to find anything anywhere that actually works. It looks like a lot of us are having issues with this. Does anyone have a solution?

    Thread Starter Windpipe the Clown

    (@ravenseye)

    Thanks for the response! I just somehow found the answer by casting about blindly on Google. I’ll post it here in case it might help others. Originally, I was trying to use this code:

    $querystr = "
       SELECT wposts.*
       FROM $wpdb->posts wposts, $wpdb->postmeta wpostmeta
       WHERE wposts.ID = wpostmeta.post_id
       AND wpostmeta.meta_key = 'price'
       AND wposts.post_type = 'post'
       ORDER BY wpostmeta.meta_value DESC
       ";

    The values returned by the database would not sort naturally. So, I simply changed the last line to this:

    ORDER BY wpostmeta.meta_value+0 DESC

    and now it does what I want it to. Perhaps if you see anything else I might be missing here, I’d appreciate your input… This level of hacking templates is as deep as I’ve gone.

Viewing 14 replies - 1 through 14 (of 14 total)