mouse over popup info box

I’m also having the same issue. That the mouse over pops up correctly but then doesn’t disappear as it should.

Yeah i saw that bug, it’s fixed in the latest standard version which you can download from our website.
From version 2.0 we will have a unified codebase and we will not have this problem anymore.

ok but I don’t see a version 2.0 on the website. I only see 1.10.9 and when you try to upload that it wouldn’t work

I said “We Will” 2.0 is the next version.
To install 1.10.9:
Can you please download version 1.10.9 standard from our website and then do the following
1) perform a db backup to be on the safe side
2) deactivate the plugin ( just deactivate it do not delete it )
2) delete everything in /home/sinoterm/public_html/wp-content/plugins/all-in-one-event-calendar folder
3) extract our zipped archive
4) copy the content of the the archive to /home/sinoterm/public_html/wp-content/plugins/all-in-one-event-calendar
5) replace /home/sinoterm/public_html/wp-content/themes-ai1ec with /home/sinoterm/public_html/wp-content/plugins/all-in-one-event-calendar/themes-ai1ec
6) reactivate the plugin
It seems you are mixing versions somehow. This would install version 1.10.9 standard.

Thank you that works like a charm! but another issue occur

What issue?

Hi – great calendar…love it.

I ran into the same mouse-over issue and followed your instructions above. It then gave me a message to update the core components of calendar. I attempted to click through and follow instructions. Now it is stuck on: /themes.php?page=all-in-one-event-calendar-install-themes

It displays:
Calendar themes were installed successfully.
[button]
All-in-One Event Calendar Settings ?

If I click the button to access the settings it says:
You do not have sufficient permissions to access this page.

I can’t access any other page in my WP admin. Everything I click sends me to this screen. Need help!

Thanks!

I had to delete the plugin via FTP. Regained access to my admin and have reinstalled whole thing from scratch. It appears to be working fine.

So the issue is resolved.