Andrew Worsfold

Hi all –

As the original author of this plugin it’s disappointing to see the new management team not responding to topics like this. I know that they are assessing their options with respect to the upcoming Gutenberg editor, so I’ve reached out to them to find out what their plans are and ask that they communicate their intentions.

Are you referring to the image and video widgets (i.e., those included in WordPress)?

This and other improvements will be included in the next release. Thanks for the feedback!

Thanks for this, @mikeschinkel!

I’ve adapted the code and applied it to the tailor_modify_colorpicker function. This change will be made available in the next release.

Hi @darbielee –

I’ve just tested on 5.5.26, 5.6.10 and 7.0.0 without issue. There must be something else going on. Is there another environment you can test it in?

Good to hear. Thanks for the update ??

Thanks, @nefariouscreations!

The key objective when developing Tailor was to create a simple, easy to use page builder, so I’m very happy to hear that you think it achieves that goal. I really appreciate the feedback ??

Cheers,
Andrew.

@simonvdsteen –

Tailor produces HTML content, which is what you’re seeing in the editor, and custom CSS. Both are displayed in the frontend without any filters being applied.

Tailor meta data (setting values etc.) are stored separately in post meta. This meta data is used to (re)construct the page when editing the page in Tailor and any changes made (and saved) in Tailor will update the content and custom CSS.

A conscious decision was made to allow users to edit content even after creating a custom Tailor layout. There are many benefits to this approach, but one drawback is the confusion that it can cause. A notification is displayed for this reason; advising users that the content is separate and will be overridden by changes made in Tailor.

Tailor fully supports post revisions, so even if you change content manually in the editor you can restore previous content (and the associated layout data/CSS).

Given everything above, the expected behaviour is: if you make a manual change to content in the editor after Tailoring a page, those changes will be reflected in the frontend. Tailoring that page again will result in the last saved Tailor layout being loaded. Is this what you’re seeing?

Thanks for the information ??

I’ll check whether it does the same thing for me and, if necessary, put a fix in place.

Hi Simon,

Tailor doesn’t support versions of WordPress earlier than 4.3 and should actually prevent plugin activation in those instances. Were you actually able to run it on WordPress 4.0?

If you’re using a Gallery element in Carousel mode with arrows enabled, this should be the default behaviour. Are you seeing something different?

Not currently, however we’ll consider this as a feature request for the future.

Thanks for the feature request. I understand what’s being asked for now and will consider adding this to a future release.

Hi @benormstad –

This is actually an issue with the Method theme, not the Tailor plugin. I’ve let the author know so that they can release a fix.

If you need to make an immediate fix yourself, the issue is due to the custom elements being defined in the bundled Method extension for Tailor. Each element is passing $general_control_arguments to tailor_control_presets() without first defining that variable. Setting it to an array removes the notification.

Hope that helps,
Andrew.

Hi @marcel –

Apologies for the delay in getting back to you. You’re right: this isn’t a feature (yet), but is something I will look to add. If you have a working version please feel free to raise a PR on GitHub.

Cheers,
Andrew.