umapper

Hi, about new map/editing – you are perfectly right – it’s already in my todo list, so that if you select map embed tag, then hit the U icon, selected map should be loaded (as this is most probably what user would expect).

Regarding changelog – I would issue one on plugin’s page, but general rule of thumb is versioning: 3.0.1 – first number is a major, you should definitely update, second one – any major fix/feature, you should update if you had any problems with umapper, and the minor numbers are mainly for maintenance (when I recompile language files, fix some typing errors etc), so most probably you do not need that update (again, if everything works as you expect it).

Would try to wrap that add new / edit map feature till the end of this week. Let me know any other findings!

Thanks for you help!

Good! I have upgraded the plugin with possible fix – and I am really happy that it did the trick! Let me know about any other issues, or possible improvements on how plugin functions.

Thanks!

That’s quite an awful issue, which makes it even worse – I cannot reproduce it on my WP installation. Can you please contact me via victor ~ at ~ afcomponents dot com, plus provide with details of your WP installation (what I might need is WP version, plugin version, OS, browser type and version). I would try to resolve this issue as the first priority.

Thanks in advance!

Now no umapper scripts persist on client side – only <object> code if map is present, but even then, no js – I made sure that client side stays as light as it could be.

I suppose you have recently upgraded to WP 2.8? If so, then this is compatibility issue which is resolved with the latest plugin release (3.0+ should work w/o any problems).
Please, let me know if you are still experiencing issues with plugin..

Ovidiu,
Thanks a lot! Examples you provided are real-time savers. Would review them in details, and incorporate similar behavior into UMapper plugin.

Well, afaik before plug-in shortcode is parsed header is already emitted. As about conditional comments – could you elaborate on this? Maybe I am missing something – if it’s doable, I’d do it from within plug-in.

Well, actually there were no definite plans to include such functionality in client-side embeds, but with the new templated architecture this sounds like something we can tackle after all.

I would forward your request to our Flash team for review.

Fixed. Please upgrade to the plug-in version 2.3.5+.

Guys, honestly, it has been answered in plug-in’s FAQ and I have stated it several times in this post, this error means you are having PHP version 4, which is outdated, and is not supported by UMapper plug-in. This error translates into human language as the following:

you have used private|public|protected (or some other perfectly valid PHP5 function access modifier) in PHP4 context.

Again, if anyone is absolutely sure he has PHP5, and still gets the error, feel free to contact me directly: “victor ~ at~ afcomponents ~dot~ com”.

Have you tried clicking the U button in Visual mode (there’s known issue with HTML Mode – which should go away with plugin release v. 2.3.7+)?

Although I have confirmed problems with HTML mode, in WYSIWYG mode there were no problems – map editor window pops up on U button click.

Please contact me (details on plugin’s page) if anyone still receives such misbehavior – so that we can sort this out.

Right now it’s included in default release, please, let me know if you are still experiencing such issues after upgrade (to version 2.3.5 +).

Plug-in should work with WP versions up to 2.7.1 now – please, let me know if you still getting this or similar error.

2Zac: you are right, error message described above, really is due to plug-in’s incompatibility with PHP4. However, there were also compatibility problems with new WP 2.7, which should now be resolved (so I post here in case someone wonders whether plug-in work on latest WP or not).

Alan,
I have answered your e-mail, giving my msn and skype details.
Have you received it?

Hi,
Yes we would certainly post an announcement here and on google groups, once this issue is resolved.

Thanks!