jaxonk

Yep. Here too. Any word on this?

Thanks for all the work on this to the devs.
I am also wondering about the ETA for the next version. Even a guess would be helpful. Thanks a lot!

Another vote for Multi-site. You have the best admin bar plugin out there, but its most useful deployment scenario is in the WPMU world and it does not work there. I, and I imagine many of the folks above, will be more than happy to donate when this functionality comes online.
Thanks a ton and please keep us posted.

To follow up here too. A huge thanks to Kevin from ypraise. This plugin is fantastic and Kevin has been incredibly helpful and polite. Not always the case with plugin developers. I know it’s not always fun responding to tons of support requests from mostly non-paying users of your software and I really want to just give a shoutout to Kevin for being so great to work with. I also want remind everyone reading this to make donations (no matter how small) to the developers of your most loved/used plugins. If WP users don’t pick up the rate of donations quickly, we are going to loose our most valuable resource, the thousands of developers that dedicate so much time to making this the incredible platform it is today.

Thanks again and if anyone else has similar issues, feel free to respond here and might be able to advise based on my experience so far.

Thanks Kevin. Email sent.

Hey there Kevin,

Thanks a ton for prompt and thorough response. I did not have any SEO plugins activated while this problem, was occurring and I did try deactivating other plugins that seemed like potential culprits to no avail. All this points to a theme conflict I imagine.

So, I tried installing SEO Ultimate as per your recommendation and set a custom meta description for Ecuador Accommodations (the link mentioned before). Unfortunately, this did not fix the issue though. Now, when I look at the source code for the page, I just see two name=”description”. First is the broken/long one, second is the custom one I added with SEO Ultimate.

So, this is a no-go still. GeoTheme is a big, fancy theme with lots of built-in features. I know my way around the code a bit, but there is tons that I am still figuring out. If you are interested in finding a solution for this for the greater good, I’m more than willing to give you access to my cPanel, ftp, wp-admin, etc. I also, have a coder-friend working on finding a fix today, so maybe he’ll come up with something that you’ll then be able to implement – or maybe not. Lastly, I am going to mention this on the GeoTheme forum as well and see if they have any insights.

Any other advice would be great. Thanks again!

+1 on this

Hey there Peter,
The blog is just a simple self-hosted wordpress blog. I will try out the plugin on a clean install on another domain and try to narrow down the issue – to a conflict, domain issue, whatever.
Jaxon

Also, I just went through the last set of instructions you sent and they wall worked fine until the last one. The URL you mentioned does not work. Any ideas?
Thanks

Hi there Peter,
Sorry for the long delay. I had spent a bit too much time trying to get this to work and had to put it aside for a while.
Today I tried deleting every reference I could find in my database, all web files and reinstalling. Once I added the oauth stuff and clicked “refresh..”, I arrived on a white page with the following error:
Could not connect to Google Latitude. Refresh the page or try again later.
The url was:
https://mydomain.com/wp-content/plugins/google-latitude-history/redirect.php?callback=%2Fwp-admin%2Foptions-general.php

I tried deleting everything and starting again from scratch. Same thing.
Thanks!
Jackson

Hey there Peter,
I just tried that twice, but no oauth token appeared. What does that mean?

Okay Peter. Got it. I went ahead and installed the new version, re-authorized and tried syncing. Here is the response:

Error setting Latitude location history
hide latitude response
{"error":{"errors":[{"domain":"global","reason":"required","message":"Login Required","locationType":"header","location":"Authorization"}],"code":401,"message":"Login Required"}}

Will do Peter. Should I add the two pieces of code you mentioned previously to this new version as well?
Also, I was just reading the other support thread and it looks like even getting this resolved won’t actually result in a working map right now. Is that the case?
Thanks for your time and the update. I’ll try it out tomorrow.

Okay let’s give this another shot then… I downloaded a fresh copy of the plugin and replaced the file with fresh code. Then added your edit below case ‘GET’. I am still getting the last error I mentioned, but now I’m also getting a more relevant looking error. I’ll post both below, as outputted after hitting “sync…”. I’ve replaced two parts with Xs. Please tell me if those weren’t the right bits to hide…

https://www.googleapis.com/latitude/v1/location?max-results=90&min-time=1318464000000&oauth_consumer_key=mangolandia.com&oauth_nonce=xxxxxxxxxxxxxxxxxxxxxxxxxx&oauth_signature=xxxxxxxxxxxxxxxxxxxxxxxxxx&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1320532700&oauth_version=1.0

Catchable fatal error: Object of class stdClass could not be converted to string in /home/mangolan/public_html/wp-content/plugins/google-latitude-history/google-latitude-history.php on line 312

Pasted the wrong error text before, but edited and corrected it now…