Andrew Worsfold

Thanks for that, @bluoma.

I’d recommend CSS over JS solutions every time for full width sections, although what you have above looks good too. I’ll look to release a more robust version for people that need it and don’t have the necessary JS knowledge.

Cheers,
Andrew.

Thanks, @bluoma! Much appreciated ??

Thanks for the positive feedback, @fraserdk!

Thanks both for your investigation so far. This may be an issue with the Slick Slider plugin so I’ll check whether there’s a newer version that addresses this.

Hi @darbielee –

The full-width section feature does appear to behave strangely in some circumstances, which I will investigate further with the goal of releasing a fix. Using some simple custom CSS to achieve the same effect is always recommended over JS, where possible.

In terms of custom breakpoints, I agree: that’s a worthwhile feature to have (especially given the defaults which are inherited from WordPress’ Customizer). Unfortunately it has wide reaching effects and is therefore quite a lot of effort. It’s on my list and hopefully we’ll see someone help out on the GitHub project.

Cheers,
Andrew.

Hi @chaleybgis – the margin/padding settings are overrides, though I see where you’re coming from. Other elements operate in the same way (default styles within the main stylesheet). Perhaps the best solution is to simply remove the default margin on sections?

It should be possible to have an “empty” section/content element by adding a space in the content element when using “HTML” mode. Does that work for you?

Do you mean the post list in the admin interface? There should be links to Tailor a page both in the “action menu” on the post list page as well as in the admin bar when editing an actual post/page..

Thanks, Mina. Your kind words mean a lot and I’m glad to hear you’re enjoying the plugin! ??

Hi @brandbrilliance –

I’m aware of some short comings of the current JS approach, but also that it’s being used by some people. Ripping it out suddenly could affect those people and it would therefore need to be done carefully.

If the quirks of the JS approach were resolved, would you be happy leaving it in?

Hi @uamv –

Thanks for the feedback. I’ll investigate potential fallbacks with a view to including one in the future. If you’re aware of one already, please don’t hesitate to submit a PR to the GitHib project.

Cheers,
Andrew.

Sidebar settings don’t require that you specify a “refresh” method, however that shouldn’t matter. How have you registered the associated control? Is it a custom section as well?

What else are you doing in canvas.js? Are you sure that file has been enqueued properly?

Hi @miturn –

The easiest approach would be to re-render the element instead of relying on a live JavaScript update. Changes to HTML markup, fetching of images etc. are best handled in this way.

Regarding your custom control: could you provide a sample of the code that you’ve written or given some idea of how you’ve added it?

Cheers,
Andrew.

Hi @phil1ooo –

Have you tried disabling all plugins other than Tailor and then giving it a shot? The behaviour you describe is unexpected and it there’s nothing inherent within Tailor that should allow you to add and delete but not edit elements.

If you still are unable to edit elements with other plugins disabled, could you please right click on the screen, select Inspect and let me know if any errors appear in the console?

Cheers,
Andrew.

Hi @hendrikje,

I’m guessing that there are two aspects to this: the builder itself and the resulting HTML pages.

I’m not particularly well versed with WCAG2.0 compliance but, where possible, I have tried to make elements accessible. My understanding is that some elements (like Tabs) could be improved and that will be the focus of a future release.

Have you managed to test the plugin to see how it does? It’d be great to get feedback from people like you who have a lot of experience with accessibility generally.

Cheers,
Andrew.