Adobe Community: Message List - R192 System Update - Scheduled to go live November 18th, 2013

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Fri, 22 Nov 2013 18:03:25 GMT

Hi,

It seems that the new Content Editor stops working when clicking from the Home Page through a menu option to an inner page.

But if you go 1st with the 'Preview' Option on the inner page you want to edit and then click 'Content' the page becomes editable. (It was working ont he old editor).

I suppose it's not ment to work in this way?

Hartmut

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 22:56:19 GMT

Thank you, Vinayak.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 20:06:22 GMT

The fix for the known issues since the release has been deployed on production and the status page was updated - http://status.businesscatalyst.com/.

lsmith6939, I have replied to your recent ticket with BC support.

Thanks,

Vinayak

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 19:45:23 GMT

Thanks Florin

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 19:27:28 GMT

One of our clients experienced the Payment Gateway's PayPal Standards information disappearing. Is this a bug from the latest release?

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 17:31:21 GMT

Hi Neil,

We've identified what's causing this and engineering is currently deploying a hot-patch to address this bug and the other issues that were discovered after the release.

The status page has been updated that the hot-fix is underway, and it will be updated again once all the validation tests are passed and the issues are confirmed fixed.

Please accept our apologies for this inconvenience - but we hope to have it fixed and confirmed within the next few hours.

Thanks,
Florin

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 17:23:26 GMT

So much for communication. No word from Adobe. I told my clients it was getting fixed.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 03:53:29 GMT

Yep, confirmed, that fix did not work or was not applied.

Anyone seeing the issues people having with addtoCart?

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Wed, 20 Nov 2013 01:05:40 GMT

No Liam, it's still not working.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 23:07:09 GMT

It was, but I was getting whitelisting at the very start this morning but now I am not (I may found a bug with the new implementation but need to test more) - Try that script fix Neil to see if that is implemented now?

I did think that conanical URL's would be in this release but do not seem to be?

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 21:32:31 GMT

So I guess it wasnt deployed, even though it says it has been in the staus. thats odd.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 21:26:39 GMT

Yeah Neil, it says it is but I am looking at things and it does not appear to have been applied, none of the features/fixes etc are in there.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 21:26:06 GMT

That was because the release was delayed Due to perfomance issues.

status.businesscatalyst.com

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 21:11:22 GMT

Florin, any news on that bug in ios for ipads?

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 18:40:01 GMT

I did a campaign yesterday and had to still whitelist the links in the email content. I manually inserted the links so I'm not sure if the whitelisting is connected to the incontext editor or what.

Can we confirm that the automatic whitelisting has been implemented?

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 16:24:36 GMT

It says the release has been completed but I still can't select a shipping option using an ipad with ios7. that bug was supposed to have been fixed. I cleared the cache and restarted te browser. No luck.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 14:21:02 GMT

Hi Florin,

Yes, your detailed answer is very clear.

Thanks and regards,

Phil

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 12:30:52 GMT

Hi Phillippe,

The above phrase refers to the old InContext Editing integration in Dreamweaver. There is no intention to remove / alter the BC integration into Dreamweaver CC.

That integration was built into Dreamweaver and tuned specifically for the old standalone InContext Editing service. The service was looking to help freelancers build very small static sites and add some editing capabilities for their customers. From this perspective, the integration intended to help and guide a freelancer to go in and define editable regions or sections on a page by page level.

But on a service like BC, which is generating dynamic pages, and where business owners and partners can create as many pages as they want from the admin interface, this model does not scale up anymore. A far better solution is to have an editor that automatically detects areas of the page that are editable and make them available to a user that wants to make some updates. And this is what we have started to do with the new InContext Editor that is included in this release.

I hope this clears out a little bit more for you.

Florin

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 05:36:33 GMT

Fubals,

The release was delayed - http://status.businesscatalyst.com/

Penny

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Tue, 19 Nov 2013 05:00:33 GMT

3659713

Fixed an issue in the check-out form that prevented users from selecting a shipping option when using Safari 6.1 with latest iOS version

Hi Florin,

I just tested this on iPad3 running iOS 7.0.3 with Safar v7.0 and it still has the same problem once you choose the shipping option, it wont let you click ok to get rid of it.

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Mon, 18 Nov 2013 19:10:08 GMT

Hi Florin,

Could you provide some details about how "Integration with Dreamweaver CC has been removed as we plan to focus on auto-detecting the regions instead of forcing users to mark-down content" affects Dreamweaver workflows, e.g. for someone who does most of their editing in DW?

Thanks!

Phil

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Mon, 18 Nov 2013 07:52:57 GMT

Hi Fubals,

No, you don't need to implement anything, it should work directly out of the box after the update is pushed live in a few hours.

Florin

Re: R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Sun, 17 Nov 2013 23:31:02 GMT

Hi Florin,

with fix -

3659713

Fixed an issue in the check-out form that prevented users from selecting a shipping option when using Safari 6.1 with latest iOS version

do we need to implement anything... or will it just work now?

R192 System Update - Scheduled to go live November 18th, 2013

forums_noreply@adobe.com — Sat, 16 Nov 2013 10:04:05 GMT

On November 18th, 2013 we are going to push live a Business Catalyst system update.

The release will include a fresh version of the InContext Editor, template support module_shoppingcartsummary and some bug fixes. For more information on the major updates coming on with this release, please check our release announcement on the Business Catalyst blog.

Issues fixed by November release

Issue #	Description
3661632	Fixed an issue in the new InContext Editing upload image interface that prevented users from adding an image tooltip because the field was disabled
3661338	Updated caching engine configuration so that it also indexes and makes available in front-end comments that are approved by Akismet
3659713	Fixed an issue in the check-out form that prevented users from selecting a shipping option when using Safari 6.1 with latest iOS version (related forum post)
3659081	Fixed an issue on Safari 6.1 that made all action buttons invisible on all admin interface pop-ups (related forum post on the paid partner forum)
3658082	Updated the Secure Domain redirect engine so that it does not checks links from email campaigns; for those links we're now using a different authenticity verification that does not force the user to white list the target URL.
3657003	Updated new InContext Editing so that it recognizes the visitor device class module
3655209	Fixed a bug in email campaigns list which caused the tree to crash when one tried to move a parent campaign under one of it's children
3655255	Fixed a bug that caused the link picker to crash when one tried to link to a module that does not exist in the current site (ex: try to link to a blog, when the site does not have any blogs)
3654651	Updated email marketing rendering engine to strip data:image tags since they are considered illegal by Amazon Mail Service
3654646	Enforced captcha validation for Add to Favorites on any new sites
3654006	Updated caching engine configuration force update a blog post content after a change is made in the back-end
3624146	Updated the site replication engine to also copy the "Disable Detail Page" web app setting
2825557	Updated site replication engine to also copy web app item addresses
3536925	Fixed a bug in the new InContext Editing interface that caused a broken layout in Link Picker editor after a window resize
3606485	Updated the new InContext Editing interface to lock down embed elements and keep the editor toolbar on top and active
3603360	Updated InContext Editor to display a warning when navigating to admin without saving the changes
3608192	Fixed a bug in the InContext Editing interface that caused an incorrect mark of editable regions
3603306	Updated Impressum and OXO templates to make it compatible with the new InContext Editing versions
3488813	Fixed a bug in the new InContext Editing version causing a broken mark-up when users duplicate a section

Known issues and limitations

This release includes the following known limitations:

InContext Editing does not allow users to edit Content Holders with dynamic names (ex: {module_contentholder,name="{bc-module} "ice:editable="content"})
- Trying to save such a Content Holder will generate a "Content Holder not found" error message
- The only dynamic names accepted are the ones generated from the {system_visitorDeviceClass} tag (ex: {module_contentholder,name="ch-{system_visitorDeviceClass}"ice:editable="content"})
InContext Editing does not offer support for editing modules inside an editable Content Holder. When editing such Content Holder ICE will overwrite the module tag with the content generated by that module.
InContext Editing mark-up is not recognized inside a Content Holder when the Content Holder is not marked as   editable, any regions defined in the Content Holder will not be editable with ICE.
For example:
-   editable regions defined inside {module_contentholder,name="some content holder name"} are not editable on   ICE
- editable regions defined inside an editable Content Holder {module_contentholder,name="some content   holder name" ice:editable="content"} are editable in ICE.
InContext Editing Toolbar
- The new editor uses the browser native Undo / Redo and Copy / Paste functions instead of having these built in the toolbar
- Clear formatting is now executed when users paste content into the editor; as a result, the clear formatting options are no longer integrated into the new editor toolbar
- Paragraphs and CSS style selectors are no longer available as the styles are inherited from the editable region container
Integration with Dreamweaver CC has been removed as we plan to focus on auto-detecting the regions instead of forcing users to mark-down content