Sheila

PS: This morning the spoilers are working. My guess would be that the jquery updater fixed it but that I didn’t clear the cache and didn’t know it was fixed. Happy it is, whatever the reason!

I was so hopeful this would fix my same problem but it didn’t! ??

In case anyone else looks here I thought I’d update to say that upon further investigation ALL the fixes are listed here: https://www.ads-software.com/support/topic/version-440-with-gn_-compatibility-mode?replies=19

I’ve successfully updated my most complex site and will now move on to do them all and finally leave v3x behind. YAY! Good luck.

So in my first test case this particular fix didn’t do the trick. BUT upon further investigation ALL the fixes are listed here: https://www.ads-software.com/support/topic/version-440-with-gn_-compatibility-mode?replies=19

I’ve successfully updated my most complex site and will now move on to do them all and finally leave v3x behind. YAY! Good luck.

I have the same issue and what I’ve been doing is keep things in 3.9.5 but I’m worried about security and also php compatibility. In the change log I found found a link to how to migrate. I’m pasting it in here for you. I’m going to see if I can make this work on my sites. But I wonder if every update will just overwrite this change.

Compatibility mode prefix is changed from gn_ to su_, how can I fix this?

Since version 4.0.0 prefix for compatibility mode changed from gn_ to su_. If you have many shortcodes with old prefix and don’t want change all of them, you can change default prefix to your custom.

You need to add the following line of code to your theme’s functions.php

update_option(‘su_compatibility_mode_prefix’, ‘gn_’);

That’s all. Now, you can use old prefix for all shortcodes.

OK, if no one can help with that, how about a related question. I’m wondering if the old version SU 3.9.5 is compatible with newer php versions such as 5.4.25. Thanks.

Done. Thanks.

Interesting…I just discovered I have a single site that made the move (still in dev in a subdomin) so the plug-ins were not kept up to date. He’s still running GA v6.4.5 with NO issues. So it’s something in the update and not the move perhaps? I mean his site moved along with the others but his doesn’t have the issue. Maybe that tells us something.

I decided to go ahead and update him to 6.4.7.3 to see if the issue happens. It does! So what is it about the update? Since I changed servers could it be a setting on the new server in combo with the update? I hope this helps to figure this out. Thanks.

Apache version 2.4.7
PHP version 5.4.25
MySQL version 5.5.35-cll

I’ve tried this already and it did not fix it. I uninstalled, re-installed and the moment I activated it I got the SAME errors. Any other ideas?

I found the answer to number 1 on the Time.ly community forum here:
https://community.time.ly/forum/customizing-your-calendar/appearance/156-category-color-in-agenda-view?_=1386190090893

I’m still curious about a better way to deselect categories.

I figured this out. It was a conflict with Advanced Recent Post Type plug-in and I just changed the setting in that and it’s fixed now.

I got this so thought I’d post in case anyone else comes by. I wanted circle thumbnails and added a custom class:

.customfooter img {
.border-radius(50%);
}

Wow, thanks for the very speedy response! I just switched to 2013 and NO it apparently does NOT happen there. I didn’t even have to turn off plug-ins. SO…I gather this means it’s a theme issue then. I can take it up with Pagelines DMS instead. I’d been noticing it for awhile. I’ll need to check and see if it happens in any other themes. But maybe not! Thank you.

Thanks for the plugin tip Randy. I’ll check it out. You’re right, performance (speed) is not at the top of the list for my clients. They want their stuff to LOOK great which Time.ly has nailed. But I’ve also downloaded Event Organiser for future consideration. Thanks.

Thanks…that helps a lot to understand! Seems like you’d do well to consider not having two free versions. That seems to add a lot of needless complexity/confusion with all those differing/corresponding version numbers…oh my!