allm

See the remarks at
www.ads-software.com/support/topic/map-is-loadingendlessly

Well, YOUR problem is solved (which is nice, I’ll have a look at mappress too), but not for all other users that use this plugin. This problem will go unnoticed for a lot of users because they are not testing with Explorer 9 AND “Tracking Protection” ON, but some of their visitors will see the “endless loading page”…

I see you have set this topic to resolved, which is not really accurate. Can you set it to unresolved again? Hopefully Alexander will notice so he can fix this otherwise great plugin.

If you have Internet Explorer 9 AND “Tracking Protection” is ON this plugin will load endlessly. I’ve seen more people complain about this. Looks like something for Alexander to take a look at…

I’ve just checked and your suggestion has worked. I’ll change all the instances where I added a class to just that. The combination used to work so this might be something that others will find too.

I’ll set this to resolved. Thanks for your quick answer!

Hi Mike,

I am really looking forward to the new plugin.

Idea #1: defining tooltips for the labels in a form.

Idea #2: no cookies. This is especially useful for European users because some countries have strict rules about that.

Idea #3: Remove some stuff from the codebase, like vCita. It will make the plugin lighter. And, of course you can provide seperate plugins that combine with 4.0 for those commercial activities.

If more ideas come to mind I will let you know.

Ah, thanks. I’ll wait for 1.6 as I have more work to do on this website. I’ll get back to this and see if my problems are gone.

One more thing which might be a problem is the handling of templates. I am using the atahualpa theme, which handles sidebars different from your templates. I could write my own templates but then I need to remember to put the templates back in the theme everytime there is an update (or if the client makes an update I don’t know about!). This is a matter for later. If I run into problems there I’ll let you know in a new thread.

Thanks for now! I’ll set this to resolved.

Hi Stephen,

Thanks for your quick reply. I have played around with this and it works a little strange. I got it to work on a NEW event, where I had to input everything OK at once. Editing afterwards gave problems. Sometimes the reoccurence is set to “custom” and the selections were not saved. Sometimes the end-date gets reset although I saved another end-date.

It is quite confusing.

Also the events calendar widget does not display ALL events, but only the first event from a series.

Hope this makes sense. I’ll clear the database and see if I can make some sense out of this and give you a better idea of what is going on and where the difficulties arise…

Just a quick update. I haven’t had time to get back to this, but hope to do so in the near future. If anything worth mentioning comes up, I will let you know.

Hi Mike,

That sounds like an answer from vCita that is avoiding the issue. In none of my websites I activated vCita (not even tried it), but in all of them the cookie is set if you access the website. If you Google for the name of the cookie you will find a lot of privacy statements from websites that found out the cookie is there as well.

Apparently the cookie is being set in some vCita Javascript that comes with your plugin. I wonder why…

And I am wondering what else is there in the Javascript from vCita that is being executed although I have no need for vCita.

I feel no need to refresh earlier vCita/privacy discussions, but it feels funny that a cookie is being set by a funtion that I don’t need and really don’t want.

I am looking forward to the all new 4.0 plugin. I hope you can leave the vCita code out and find another way to make some money from getting customers for vCita. It seems they have their own plugin now, so maybe there is another way…

All the best with the work on 4.0!

Hi YOP,

Thank you for the quick reply and update! I deleted the plugin for now, but will get back to it next week or the week after. I’ll let you know what happened.

The answer to your earliers question: the problem only happened with the plain WordPress text widgets.

I’ll let you know later.

Thanks again!

Hi Tristan,

I haven’t checked your source code, but if the content that is enclosed in a shortcode contains (or may contain) other shortcodes you need to output do_shortcode($string) instead of $string.

Hope this works for you.

Will check back here in a couple of days to have a better look at your plugin.

Are you looking at the site with IE9? And do you have Tracking Protection enabled? If so, that might be the problem. The call to the Google maps API is rejected. If it works OK in other browsers or IE8 then the “IE9 / TP problem” is the culprit.

All Google maps plugins will be suffering from this, but the way the plugin handles it varies from plugin to plugin.

Did some more digging into this.

In IE9, press F12, click script. Then load your page with the map. It will probably give you some warnings about https://www.google.com/jsapi?ver=3.4.2 being blocked because of Tracking Protection.

Tracking Protection can be found under tools / safety (Alt X, safety)

As a website builder it seems there is nothing you can do, to get this to work. It is up to the individual user to disable or enable Tracking Protection lists.

Disabling Tracking Protection lists will immediately solve the problem in this topic.

I am not comfortable with disabling TP though. I am not sure how many users have TP enabled.

Or is there something the plugin author can do to get this fixed.

The above seems to indicate that changing to other plugins will be of no help.

Or am I wrong? Any ideas out there?

Same issue here using IE9. Firefox and IE8 (!) seem to be OK.
Can the author of the plugin shed some light on this?

Hope he sees this as this is on his website:
Please note – I am in the process of relocating to US these days (as of 21st of March). Until further notice no new features will be released. Only bug fixes. Might not be able to respond as quickly as usually.

Oooops! Even after using this plugin successfully on some other websites, on various hosting platforms, I missed something. The solution to the problem above is soooooooooo simple. I forgot to set the “Data Export” checkbox in the FSCF form definition. That’s what you get when you restore a backup of the form definitions from another site and do not look at it in detail…

I lost some time on searching for a solution, and I hope no one else wasted time on this…

I’ll go hide somewhere for an hour (but happy it works now!)

I’ll set this to “resolved”

??