Bug found since Monday's Groupsite changes
2 followers
0 Likes
We had a couple of features stop working or change how they work - these features worked perfectly before Monday:
1. "Share button" used to post to other social network sites (a button "widget" that uses a pop-up menu to post to Facebook, Twitter, etc.). It does not have a fixed height.
2. Google Ads are not working correctly either - they are creating some sort of error that is stopping our Javascript menu system from displaying - When I removed the Google Ad widget it started working again.
You can view http://santaluz.groupsite.com/main/summary
also http://ebonsella.groupsite.com/main/summary
Let me know if there is a work-around - we really need to have these features working like before. Thanks for your help.
6 Replies
Reply
Subgroup Membership is required to post Replies
Join Groupsite Champions now
Suggested Posts
| Topic | Replies | Likes | Views | Participants | Last Reply |
|---|---|---|---|---|---|
| RSVP invites not going out | 5 | 0 | 2652 | ||
| XML Export not working | 4 | 0 | 2100 | ||
| Deleting an Empty Category | 1 | 0 | 1480 |
Hi, Mark - We did make some security improvements to the content modules, and sorry for any transition pains. Thanks for writing in so we could help.
Regarding the "Share button" - we noticed 2 things about this particular share widget: it's getting cut off to the left when you click on it, and it doesn't naturally have a "fixed" height. These things are due to how we now handle embedded javascript, not a bug, but if we missed something else let us know.
This may help:
1) A sidebar module is 300 pixels wide, and your current widget is too wide for the space. You may want to check with the source of your widget to see if you can get embed code for a more narrow one. As long as your widget is 300 pixels or less in width, it shouldn't appear cut off when you click on it.
2) While this widget doesn't naturally have a fixed height, there's no getting around the need to pick one. You might want to try making it taller, like 320 or 350 pixels, and then placing it toward the bottom of your page if you have extra white space.
Regarding the Google Ads - we don't know why they wouldn't be working and we have lots of folks successfully running these. If it happens again (or if you can recreate it) can you submit the issue to support? If it's not possible to recreate on your home page, maybe try it on a "More" page or in a test Groupsite.
In order to help, we'd really need to see it happening to troubleshoot.
Regarding the Google ad widget - because the error is in the Google ad javascript, it only impact javascript that is run after. Therefore, if someone has a google ad with no other javascript on their Groupsite page, they won't notice anything wrong. Please note this - you might see other people reporting problems with add-on widgets running javascript, when it is reality the Google Ad widget has the issue. I removed the google ad temporarily. I'm reinstalling it tonight and if there is still an issue, I'll let you know.
Mark,
The change we made on Monday is that if you have a content module that has a <script> tag in it, it will be "sandboxed". What that means is that in the place in the page where the content module should be rendered, there will actually be an <iframe>. The content module will be loaded in the <iframe> off of a different domain name, which provides better security. It also means that errors in one content module won't prevent content modules on the rest of the page from loading.
So with regards to the google ad widget, make sure to put it in it's own content module and it shouldn't affect any other content. Also, I'd be curious to see the google ad javascript on a page so we can see what the error is. As Diana said, other customers are using google ad javascript without errors.
Hi Diana,
Our Flickr widget suddenly stopped working (since recent changes). We have been relying on this to showcase our recent events and this is a bad hit.
Our address is http://benchmark.groupsite.com
Please help.
Regards,
VK
Vishwadeep,
This has been fixed. Sorry for the inconvenience.
Hi Paul,
I just found that this has been fixed. Thanks.