Oct 16, 2018 8:39:44 AM
Currently, in our Third Generation Editor we do not allow access to edit the HTML and have no immediate plans to do so. We want to provide our customers with the abilities to be able to use a user-friendly interface instead of having to rely on a code view to get their desired results. With all the feedback we have been collecting we are planning on making improvements to padding and adding some line spacing elements in the UI. I know this doesn’t solve all use cases, such as adding tables, but we will continue to make strides towards improving the editor.
I understand allowing HTML would increase the ability for more control of your content but it can also have a negative impact on your newsletter’s display in email clients. If we provide access to HTML for every block, changing some of the default styles or content could break display when sent to an email client. Also being able to manually adjust width could have a negative effect. We have a team of amazing engineers constantly testing our templates in all email clients, so you can be certain your email displays consistently across the board. With that in mind, we want to make sure we make it easy to provide the best look and feel not only on the desktop but on mobile. With a majority of opens now leaning towards mobile over desktop we take that as a priority.
Please continue to let us know your thoughts on HTML and what exactly you're trying to do so even if we don't have HTML access we will be able to give you the tools to get your desired outcome.
I'm very sorry for the frustration that the lack of HTML access is causing. You're correct, we do have quite a bit of useful feedback regarding HTML editing in the Third Generation Editor, and there's been a number of changes and additions in response to that feedback. While I do not know the full reasons that the design team has not implemented this yet, I do know that one of their primary concerns is making sure that the product displays good looking emails to all of your recipients. Many of the uses for HTML that I've seen, simply do not work on some modern devices, or require very intricate coding to keep mobile responsiveness. If you would like to access HTML coding, there is the option to create a custom code email.
We can add you to the list of general requests to add HTML editing directly to the Third Generation Editor, but if you can share with us your goal for accessing the HTML, we can also file additional feature requests for those specific features, which I believe are likely to get implemented sooner than general HTML access outside of the custom code emails.
We need access to the HTML for a several reasons:
Thank you for reaching out with these helpful details on why you would like access to the HTML of your emails. I apologize HTML access in Third Generation Editor is not currently a feature we provide! This is however a feature we are collecting feedback on. In fact, I have tracked this feedback along with these reasons you listed in your account.
Yes. Those and more reasons. And as someone else said, how many comments do you need to collect about what we are all trying to do that we need html for, before you actually do something about it?
Thank you for reaching out to us. I apologize for any inconvenience that may have been caused. At this time we do not currently have an estimated time for when any features will be implemented. We will continue to collect feedback as we are trying to collect as much information as we possibly can, so that the correct department can review these requests and make the best decision. I want to apologize once more for any inconvenience. If you do happen to have any requests, feel free to pass them along and we will pass that feedback to the correct department. Please let us know if there is anything else we can assist with today. In the meantime, have a wonderful day!
Is this just the corporate tagline for, "We're never going to do it but we need to keep our customers. So tell them we're collecting their feedback so that they feel like we're listening to them"? It's been a year since the question was first asked. I think it's time someone addresses it appropriately other than, "We're collecting feedback and we don't know if/when there is a timeline for addressing the one concern from multiple people."
I think that pretty much sums it up.
My other thought on this is that you would think they would stop offering us the opportunity to "accept" their "solution" as helpful. But every single comment from a Constant Contact employee both offers this and "apologizes" for the inconvenience of not being able to access the code.
I also am very frustrated by inability to get into HTML! Unfortunately none of the templates are exactly right for us, out of the box. I chose the closest one, but want to create a photo header that exactly fits across the top, not floating in space like it is in the template. I can't see the width of the column to make it the right size. I can't assume it will resize properly without distortion or pixelating if I eyeball it, and I don't want to make it really big and let it size down, because my original photos don't support that. I just want to know - how many pixels wide and high is that block!
I frequently used to go into HTML to adjust things that just don't look quite right. It's just easier. For example when I import something that's in a list and the tags don't come in right, so things are nested that shouldn't be.
The average pixel width of the header is 600 pixels, for all of the standard 'basic' templates. That's true of most of the other standard templates as well, though if you search for anything with the 'wide' tag those are 800 pixels. The height does not matter, as the block's height resizes automatically based off of the content. There are a few other exceptions, but that should be the same across the vast majority.
Every image in the new editor is meant to be easily re-sizable though, so click the two-pointed arrow in the bottom corner of it, and dragging downwards, should make essentially 'any' image full-size, without significant distortion. The new editor is better at resizing images than the legacy editor, though it's admittedly less precise.
We are always looking to implement further upgrades to the system. Some additions, like html access, have other implications which cause delays, or prevent us from enabling them easily for all customers. We won't release an update if we fully believe it will cause more harm than good, but we do take your feedback very seriously. I can honestly say that internally there's a lot of discussion throughout all levels of the organization about how best to give you the tools you want and need, while keeping the system as stable and reliable as possible.
After several years and numerous requests by users, it's become obvious that CC really has no intention of every re-integrating HTML editing into the 3rd Generation Editor. You've opted to focus your editor on the simplest and most-elementary user while leaving those of us who consistently used the previous HTML to make adjustments to the basic templates. Time to look for another service.