Andy Mercer

Yep, I was typing as you responded. (Really appreciate the quick support btw!) It’s all working correctly now. Hopefully this should be the last request for a bit, lol.

Thanks again for the amazing theme!

Nevermind! After I posted this, I figured it out. It was under Display Conditions in customizer. There were some inherited specific pages, probably from the started site. I switched the conditions to site-wide.

This leads to a suggestion: There are a bunch of options on the Blocksy page options, when editing a page, which are defaulted to Inherit from customizer. I’d suggest having an option there for “Sticky Header Transparency Functionality”, with an Inherit, Disable, or Enable option.

Gotcha, I’ll try that out, thanks! I just figured it might be easy to copy/paste the options code since it already exists for another place.

Oh, actually I did have one other small suggestion though. When the modal is open, I keep trying to cancel it by clicking on the overlay. Nothing happens, because I have to click on the X button at the top right. Many modals allow a click on ANY of the overlay background area to close the modal. It would be cool if that was an option as well.

Thanks for the info! Also, I should have started with, I friggin LOVE your theme. It’s the best Gutenberg theme I’ve seen so far. So thank you!

Now on to the specific points.

1. I’ll investigate. Thanks for the pointers.
2 & 4. That is wonderful. I’ll use the base URL + the #account-model portion as the fallback when an unauthenticated user tries to access a protected page, which lets me avoid the WP login page completely.
3. Not really my issue, but still great to hear. More translations are always better.
5. Makes sense.

One additional question. It would be really cool in the “Account” settings in customizer, if you could have the ability to toggle between “Sign in”, “Registration”, and “Both”. So be able to have the double form, or just a sign in form without the sign up. Or even just a sign up form. There are times when I don’t want external users being able to register.

And to finish, I want to again reiterate … Blocksy is just awesome. I’ve only now gotten into Gutenberg and WordPress in general after about 4 years, and it’s so completely different. Everything is so easy now. Seriously, thank you for this theme.

• This reply was modified 4 years, 3 months ago by Andy Mercer.

To add to this, I’m restricting certain pages to admins only. Right now, many plugins handle this by redirecting a person to the official WP sign in page.

When I click on the log in header link, it shows the modal, and it appends to the URL: “#account-modal”. However, if I copy that URL, with the new appended portion, and open in a new tab, the modal doesn’t show automatically. Which means there is apparently no way to deep link to the modal form. If there was, then I could redirect to it, and skip the build in sign in page completely.

I think the best way to handle this would be to make the login and sign up forms that Blocksky puts into the modal, copy them as Gutenberg blocks. Then I could just put them onto any page and deep link to it. Then add to the customizer settings the option for a fallback no-JS URL, and I could use the page I created. It would solve both problems.

I got this to work by creating a custom block called “Page Wrapper”, and limiting the child blocks that go in that. I then set a page template to only be the “Page Wrapper” block, and nothing else.

See https://wordpress.stackexchange.com/questions/353485/gutenberg-restrict-top-level-blocks-but-not-child-blocks/353640?noredirect=1#comment516509_353640 for details.

Thanks for the suggestions!

I’m going to look into 1, or into creating my own custom Heading block. Option 2 isn’t really an answer, because it’s completely unsemantic.

The answer to this is that it’s not really feasible. To work around it, I’ve created my own multi-column page section block.

Hi there, zhuraavl,

To get the caption, you’ll use the wp_get_attachment_caption function. You’d pass it the ID as a parameter, in the same way that you pass the ID to wp_get_attachment_url.

Hi there!

I did some investigation and currently, it’s not possible to even select videos to be added to the featured gallery.

I’ve been thinking about this and my opinion is that that is the correct behavior. The problem lies with the HMTL output. FG stores attachment IDs, and then retrieves them. There is no information stored about type of attachment (image vs video). The HTML will need to be different for a video, vs an image.

It boils down to this plugin isn’t really the best tool for handling videos, and currently, the answer to your question is that it isn’t possible; I’m sorry.

And to anyone else reading this, the plugin works perfectly with 4.9.6.

Since it’s been a month, I’m going to assume that you aren’t going to respond to this. Just FYI, leaving 1 star reviews instead of opening a bug ticket, and then following it up by ignoring responses, is a pretty shi**y thing to do when people are offering you software for free.

I just pushed out an update to Featured Galleries. It’s a top to bottom rewrite, and includes the fixes you suggested as well as some others that should further insulate the JS.

Since you haven’t responded here, I’m going to assume that you figured out which other plugin was conflicting and causing the error.