Can I get a straight answer regarding the shortcode editor?

Dear Rad, Alexander and Themeco,

Thanks for conversing and in the spirit of openness…

When I eventually update my v1.1.0 sites, my workflow performance will reduce to 10 percent as a direct result of developmental decisions made by Themeco. My principal sites on PRO alone are 45GB in size and contain over 100 million words which will also need updating.

Regarding your comments pertaining to the elements, they have depreciated in part, as I cannot access them the way I had and as per the response from Rad, ‘distant versions’ and ‘major changes too in order to make them compatible’ confirm this.

Regarding adding images via the Rich Text Editor, please fix the ‘p tag’ problem, then add the image link in the HTML part of the editor. Whilst considering this, reinstate the shortcode generator modal to incorporate the v2 elements to make them, your new tools and features available in the cornerstone page builder and not in the WordPress post editor.

My coding is not rare, it appears that the choice was made to recruit more sales and to target a lesser intelligencer and not to support the existing clientele. I am not against visual builders, I just believe that there are better options available and not to recklessly sacrifice those that code.

The nesting of v1 and v2 element shortcodes within text is essential and if this is not an option, then yes, you have degraded your editor?

I am not wanting to be difficult, but it appears that the workflow methods I employ are now abandoned and when you suggest using other page builders, then why use X theme at all?

Should I upgrade my sites or will I be trapped?

Best regards

Eric

Hey Eric,

The answer to your question is tricky because on one hand, embracing a new workflow sounds bad for you so the old version is the answer. On the other hand, compatibility, security and bug fixes are very important matters too and upgrading to the latest version is the answer for this.

Personally, I’d choose upgrading because security and bug fixes are very important.

For the workflow, it would require 3 things to be able to generate shortcodes:

  1. You need to enable Show Legacy Shortcode Generator in Pro > Settings
  2. Create a new page. This will be used for shortcode generation.
  3. Install the Classic Editor plugin

Everytime you create a page using the Content Builder, you need to open the shortcode generator page in a separate tab to copy shortcodes from.

The Shortcode Generator would be available beside the Add Media button.

Regarding the <p> tag problem, please copy your site to a staging server and update Pro in the staging version to see if this issue persists. If it does, please open a separate thread and give us the URL of the page in question, details of the issue and access to your staging’s WordPress Admin.

To your question:

A page builder is just for content. A theme is for your overall website design. For instance, you’re using Pro and it has a Header and Footer builder so regardless of the page builder you use, you can create a custom header and footer design.

X and Pro also does have unique design and functionality that couldn’t be powered by a page builder. In the future though, a Layout Builder would be possible so you have more power to customize areas of your site like the blog page which is currently only possible by modifying the template file. See https://theme.co/apex/forum/t/status-report-december-4-2018/48648. That is further reason to upgrade.

Our products are also updated or improved due to general user demand and new features are not created just for new or potential users, old users request improvements too and that’s how features in our products are born. In favor of new features though, some features must be put into legacy mode like the Shortcode Generator so new features become the standard.

Regarding v2 elements, they were not meant to be manually coded and it’s impossible to do so because they could only be generated and edited by Cornerstone or Pro’s Content Builder.

Thanks.

Dear Themeco directors, Rad, Alexander and Christian.

With all due respect, Christian, did you understand what I wrote before you responded?

I absolutely consider security and bug fixes to be of paramount importance and this is why I am deeply concerned and even though the new workflow is pathetic, I believe that I have no choice but to upgrade.

I do know how to generate shortcodes as a workaround and regarding the content builder, you are simply wrong. Cornerstone is part of pro, which means that any existing page developed with these elements are specific to that builder and cannot migrate without conflict.

I feel that I and my opinions are of no concern to you or to Themeco, as there appears to be no room for manual coding practices and that is a mistake and just to be clear, I believe that Pro is outstanding but is left wanting.

Please see to it that the directors of Themeco see my posts and comment directly.

Best regards…

Eric

I answered your questions based on my understanding of what you wanted and I believe I have answered accordingly except for the the Legacy Shortcode Generator part which you can ignore. I’m sorry I missed the previous discussion on that

I’m also sorry if you already know what the benefits of upgrading are. I just answered your question if you should upgrade your sites or not and I gave the pros and cons.

Regarding this:

Yes, Cornerstone is integrated in Pro and I referred to it as:

I use that interchangeably though so sorry for the confusion.

Still referring to what you said above, I believe your talking about migrating Cornerstone data to another page builder? I didn’t say anything about migration. We assumed you already understood that so we are referring to the creation of a new page using other page builders. If there’s still a misunderstanding here, please elaborate.

Now to:

We take each and every customer’s opinion seriously but that does not mean that every opinion or feature request should be implemented. Alex already explained why the shortcode generator workflow changed. It’s not what you wanted but he explained the majority of users wanted more options.

I’ll forward this to our leadership team for review.

Thanks.