swag

Thanks for the suggestion, FranceImage.

Thanks for the plug-in, Peter. But clearly I’m not doing something right when adding [geotag] to my posts to display a Google map.

I’m running WP 3.5, but there is no “admin settings page” I can find per the FAQ here. And while I can get a Google map to show in my post by including [geotag currentpostmap=true], it seems to ignore the saved coordinates in the post (and verified in the db) and I only get a nice view of ocean.

I plug in the same coordinates into my old geopress tags, which I am trying to migrate off of, and everything looks fine.

Is there a supporting plug-in you recommend to use GMaps in posts along with this plug-in, such as Geo Mashup?

Same problem here as well.

This is turning into a form letter. Generalissimo Francisco Franco is still dead. Yes, this plugin still fails.

So I tried the new 1.7.4.2 release. Got the same “Plugin failed to reactivate due to a fatal error.” message as I did with 1.7.1 RC 1.1 and RC 1.2 and 1.7.4.1.

And, as in all those previous cases, I refreshed my plugins and found that it was supposedly activated anyway. But yet when I edited posts or viewed my Web site, the features it supports were still either missing or broken. No tag cloud. No tag window in the editing pane.

Once again, for the fourth time, I reinstalled 1.6.6 with the WP 2.9 compatibility conditional hack. That is all.

Btw, I tried the new 1.7.4.1 release. Got the same “Plugin failed to reactivate due to a fatal error.” message as I did with 1.7.1 RC 1.1 and RC 1.2.

And, as in those previous cases, I refreshed my plugins and found that it was supposedly activated anyway. But yet when I edited posts or viewed my Web site, the features it supports were still either missing or broken.

Once again, for the third time, I reinstalled 1.6.6 with the WP 2.9 compatibility conditional hack. This is getting a bit monotonous.

I twice ended up revering back to Version 1.6.6 with the WP 2.9 compatibility conditional hack. Both 1.7.1 releases failed to do half of what the previous version did.

Also got the “Plugin failed to reactivate due to a fatal error.” on the upgrade with WP 2.9.1. I ended up rolling back to a hacked st v1.6.6.

I did research a fix that was the only thing that worked under these conditions.

In Settings -> General, I’ve had “WordPress address (URL)” set to https://www.mydomain.com/mysub/ and “Blog address (URL)” set to https://mysub.mydomain.com/. Since version 1.x.

By making them both https://mysub.mydomain.com/, I could get preview to work again. Which makes me absolutely puzzled as to why WP 2.6 would continue to offer two options for the blog URLs if the do not work if different…

OK, I think I found the root of the problem. It has to do with how the WordPress codebase handles installs on one subdomain when the posts show up on another subdomain.

This used to be a maddening problem with the basic post management screen. The main post management screen would hit “www.domain.com/mysubdomain/wp-admin/edit.php” just fine. But click on the pagination for it, and the WordPress PHP file would flip to “mysubdomain.domain.com/wp-admin/edit.php?paged=2” and result in a 404.

Now I see that the preview PHP is introducing the same mistakes that the edit.php files finally fixed in WordPress: previewing to the URL “www.domain.com/mysubdomain/?p=45&preview=true” works like a charm and comes up fine. But now the preview function is forcing “mysubdomain.domain.com/?p=45&preview=true” which returns a 404.

Maybe there’s an .htaccess URL remapping hack I can use here. But really — there’s no reason why WordPress should fix this problem in edit.php and at the same time introduce it in the preview URL generator.

Just started experiencing this with the first time since my upgrade to 2.5.1 this week.

Not resolved for me though. Problem has nothing to do with finding the preview button or screen. Ever since my upgrade to 2.5.1, the preview pane still hits URLs of the format: “https://blahblahblah.myblog.com/?p=45&preview=true”. But that URL format now always returns 404s for any unpublished files.

This looks to be a continuation of the unresolved problem discussed here:
https://www.ads-software.com/support/topic/127363?replies=3