CONSTANT CONTACT'S REPEATED FAILURE TO SAVE EDITS

[nancyf38915]

Constant Contact repeated fails to save edits and after working for hours when it looks like it has finally saved them (after repeatedly inputting changes) you send out an email only to find that some of the older edits have changed back!  This is beyond frustrating.

[William_A]

Hello @nancyf38915 ,

Did you perform a test send prior to the live send, and all the correct edits were in it? Is this issue occurring in other browsers, or just one in particular? Does it occur in incognito / private mode, or when you disable browser extensions, ad/pop-up blockers, or any VPNs you're running? Does it occur on other devices or networks?

[nancyf38915]

Tried the test send -- also gave reformatting/edit problems

Always used Chrome browser -- using Guest Mode

No changes to browser ext, ad/pop-up blockers, vpn's 

Using same device as always

Yes, occurs on different networks

[William_A]

Does the issue occur with freshly made emails, or direct copies from the original email campaign source?

[nancyf38915]

It was happening with copies of emails - we use the previous email as a template for the new email each month.

[William_A]

When the error occurs for you next, are you able to provide a screencap of any console errors? You'd do this by:

1. Waiting for the error to occur
2. Typing CTRL SHIFT C on PC or CMD SHIFT C on Mac
3. Clicking on the Console tab that appears
4. Screencapping any messaging highlighted in pink/red. They will also typically have "ERROR:" and a number included.

[nancyf38915]

The only error message that occurs, is sometimes there is a red bar across the top of the page that says unable to save.  Other times, it appears to save, so there is not really anything to show.  The problem, it is frustratingly difficult to have to go back through every edit made -- typos, formatting, rearranging content, etc. - to find out if any didn't stick.  Some of the time, edits will seem to stick and the test send copy will show the edit, but then when you go back in to finish up older edits have been undone.  

[William_A]

I mean the actual console code errors, which can only be viewed if you explicitly put in that CTRL SHIFT C command I mentioned. This will cause a large side window to appear in your browser, and allow you to check the console to see what explicit code errors are showing. Our devs are needing this info to narrow down the source of the error. 

[nancyf38915]

Understood. Will do as directed and share.

[nancyf38915]

The document I was working in completely froze today part way through editing. I did CTRL SHIFT C and took screen captures of code.  Logged out and logged in again, sent a test to inbox, and this time it looks like the edits stuck.