philbee

Perfect, works beautifully now, thanks a lot!

Thanks for the feedback!

Update: it was my (ancient, and very much urgently needing an update) theme that somehow prevented the popup from even showing.
Switching to a default theme, enabling Ninja’s full WAF, and then switching back so far worked.

Hey Monica,
thanks for the very detailed and interesting heads-up!

The site in question will be secured in any case (not yet certain if by WordFence, SecuPress or NinjaFireWall) – as I said, the client is very concered about security.

Even with the firewalls and all, putting full admin access to the clients Salsa account into the DB will almost certainly be a no-go. I just hacked your plugin to get the sensitive Salsa data from constants defined in wp-config.php, which might be a tiny bit more secure or less prone to mySQL hacking, but even this might not fly. My guess is we’ll have to somehow do without the Salsa API, at least until Salsa modifies it to be more modern and secured.

Or are there ways to make an admin access to a Salsa account “not too valuable”, as per the text in your class-gf-salsa.php?

Thanks again!

Nope, I was just being curious.

Having these options would actually make me buy your plugin in a heartbeat. (BTW: what are you planning for the advanced image block? ??

I’m thinking about a very specific project I’ve been working on, where Kadence’s Row Layout Block offers almost exactly what I need: the ability to simply and visually select between a single block row, a 66/33 or 33/66 row and a 33/33/33 row.

However, Kadence also offers a lot of options we’ll never ever need for this project, like all the other row layouts, background colors, margins/padding per row/column – these are the ones I’d really love to be able to deactivate or hide.

Then there are the options that always will be set exactly the same, like gutter width/right-margin, and top-/bottom-margin. For these an option to set a fixed value, for example on a “Kadence > Row Layout Options” page, would be awesome.

While having these options is perfectly fine generally, very much in keeping with what Gutenberg is all about, and while Kadence does it really nicely, I can think of many situations where one wouldn’t want these options to be visible/changeable, at least not for non-admin users.

Cool ??

Hi,
actually, I played around a bit and it’s pretty simple – in my 3 columns example, the 66% block (eg right block in a kt-row-layout-right-golden row) needs to have flex: 1 1 {width of margin}; or as a separate CSS flex-basis: {width of margin};

(margin-right = Gutter)

See https://davidwalsh.name/flexbox-layouts

The Kadence plugin is really nice, BTW!

• This reply was modified 6 years, 3 months ago by philbee.

Nice work!
Displaying Posts as Gutenberg blocks now works.

Also, I sometimes can find/select custom post types.
“Sometimes” because the finding/selecting does not work reliably – I get “The editor has encountered an unexpected error” (see error code at the bottom), even when I set the CPTs “show_in_rest” => true. Other CPTs have resulted in “This block has encountered an error and cannot be previewed.” error messages.

What is a little bit worrying though is that CPTs that seem to work in Gutenberg, displaying just fine in the Gutenberg editor with post image, title and text, simply disappear completely when viewing the post in the frontend.

(I’ve made some screenshots if that helps?)

Error message copied from “editor has encountered an unexpected error”:

Sg@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:142:332
m@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:12:390
Xb@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:79:172
https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:88:371
rd@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:91:27
O@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:90:457
yh@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:104:146
lg@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:90
mg@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:120:388
gc@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:127:204
vb@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:232
ub@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:126:67
zd@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:124:451
ra@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:123:321
enqueueSetState@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react-dom.min.82e21c65.js:189:233
setState@https://gutenberg.test/wp-content/plugins/gutenberg/vendor/react.min.ab6b06d4.js:18:456

promiseReactionJob@[native code]

@chouby

Yep, “negative values in ‘cat’ query var should not exclude the language filter” did it, works perfectly again.

Will this be in an official 2.2.1 release soon(ish)?

Thanks!

Yay, the crawler is nice!

Just one question: I noticed that my portfolio custom post type is not being added to the crawler sitemap. The CPT is found by LS Cache, it is visible in the “Available Custom Post Types” list on Settings > Crawler, but it’s not in the crwalermap.data file, and generates LiteSpeed Cache Misses.

Could you give some more infos as to “you can use filter litespeed_crawler_sitemap to append them to sitemap”?

Thanks, Phil

Yay!

Hi Scott

I might actually get in touch, out of curiosity, but at least I now realize I probably shouldn’t have written “best” but rather “fastest” managed WP (Kinsta, Pantheon and Pressidium, IMHO).

As you said: going into more depth might turn this touchy subject into a discussion forum, so I’ll be nice and quiet now.
(Actually, it’s time for bed)

Thanks,

Phil

• This reply was modified 8 years, 2 months ago by philbee.

Hi Scott

wow, that’s what I call an exemplary reply!

I probably simply was blind to the NGiNX warning when I first installed SpamShield, a bit over a year ago. I did read (and even know a tiny little bit) about NGiNX and .htaccess. Unfortunately, changing the hosting provider is not possible at the moment – but then I guess you know that a lot of the best managed WP providers run NGiNX-only setups ??

I’ll be switching to another solution for the time being, and patiently wait for some NGiNX goodness from you guys.

Thanks again for your time, and for SpamShield, of course!

-Phil