Giorgio25b

Awesome!

Thank you.

@bfintal Version 3.0.5 addresses the previous versions issues in a way that is just outstanding.

Excellent work #Stackable and thanks for pushing a much better UI/UX.

Tested on 3 different sites and it went really smooth on all of them.

Thanks @cteduard you are right and I have to apologize for pinning the error on Blocksy while it was clearly my fault.
I just assumed it was a similar issue I had in the past with the TwentyTwenty theme and I did not do my due diligence checking what the problem really was.

Many thanks! This framework is just awesome.

@cteduard I just updated the ticket, my bad, I used the wrong dev link, this is the correct one:

https://dev.fathomscientific.ca/

Same issue as describe above. Thanks

@drawmyface Thanks!
the css temporary fix/hack is appreciated but I just wanted to point out the issue; I was not aware of the Github 5876, though it has been open almost 5 years.

Thank you and since the workaround works for now I close this thread.

.wpcf7-form .contact-form label span { 
    // magic happens again;
}

Shortcode does work! I missed the part where it needs the space between the words roomlcoud and hotel:

[roomcloud hotel=’###’]

In regards of the +function(){}; my bad! I missed the part where:

`It forces the parser to treat the part following the + as an expression. This is usually used for functions that are invoked immediately, e.g.:

+function() { console.log(“Foo!”); }();

Without the + there, if the parser is in a state where it’s expecting a statement (which can be an expression or several non-expression statements), the word function looks like the beginning of a function declaration rather than a function expression and so the () following it (the ones at the end of the line above) would be a syntax error (as would the absense of a name, in that example). With the +, it makes it a function expression, which means the name is optional and which results in a reference to the function, which can be invoked, so the parentheses are valid.

+ is just one of the options. It can also be -, !, ~, or just about any other unary operator. Alternately, you can use parentheses (this is more common, but neither more nor less correct syntactically):

(function() { console.log(“Foo!”); })();
// or
(function() { console.log(“Foo!”); }());`

There is a + sign in front of the
+function ($) {
at ekko-lightbox.min.js

Is it going to be fixed? Is the plugin maintained at all?
Please advise, thank you.

Is this happening @webwavesca? Are we forking this project and move forward on a different ownership? @thompsonpaul @buddylove72

@strelok1911 thank you, but Polylang allows a multi-language website without creating a new .mo file, it’s basically a link between 2 pieces of content in different languages.
Polylang hooks perfectly almost everywhere with Blocksy, but the Customizer enhances custom widgets that are not translatable.

Anyway, it could be that the solution lies in between the theme and the plugin approaches, so for the time being I’ll work around it with this plugin that does the job (for now):

Add Polylang support for Customizer

Thank you!

I’d start in looking here:
WP Localization files

If the DE lang package is not yet there you might need to create one first.
See documentation above

@all WordPress participant to this topic:
this ticket has been marked as resolved because the developer (@anlino) fixed the bug in the Chaplin theme (which this ticket originally belonged).

If you want to follow-up on the TwentyTwenty theme similar issue and the above suggested patch (thanks @bdcstr), please use this core track ticket here:
https://core.trac.www.ads-software.com/ticket/48916

Many thanks,
Giorgio

@rockfire just a quick follow up:
I’ve been able to create a basic snippet to post Yoast meta data into the user object ./wp-json/wp/v2/users

Test live here: https://ssws.ca/wp-json/wp/v2/users

The code is here: Yoast User Meta Information 2 WP REST API

Thank you @rockfire
I will close this ticket and we will wait for future release on the issue.
Cheers

@elhyaban in the right sidebar change the status of the ticket to RESOLVED

Tickets Sidebar

Cheers

and BTW, good catch on the JS details:

// Determine offset
// var originalOffset = $target.offset().top + $win.scrollTop();
var originalOffset = $target.offset().top;

Cheers