WordPress | WordPress subversion repository | Content Management System library

I solved this by upgrading to the latest version of nodeJS

where can we at least look at all possible things like that?

Aiui the source code of the Rakudo compiler is as good as you're gonna get.

It looks to me like EXPORTHOW is processed here, with DECLARE in particular here, as part of World.nqp.

Afaik the World class is:

• An internal implementation specific detail of Rakudo. It is not part of the Raku language. It is not something you can rely on. It is not officially supported.

• Written in nqp. nqp is not Raku. It's essentially a small subset of Raku focused on being a good programming language for writing compilers.

We figured this out by going into our bing web tools and disabling the Clarity integration.

Thanks to guidance from @Tinxuanna, I've managed to solve the issue (finally!).

For anyone else having similar issues, here's what I did:

1. Access the /etc/hosts folder
2. Find file called hosts and open it in a text editor.
3. Remove the IP addresses related to vagrant (I kept a backup of the original file just in case)
4. After saving hosts file the IP addresses removed, I ran vagrant up --provision
5. I then ran vagrant up
6. Then accessed vvv.test
7. You're done!

"it does not work, $ids is empty."

That block is one of the default wordpress blocks, aka "core blocks". In order to have access to its data you would need to use parse_blocks function not get_post_gallery. That's why your variable is empty.

So the overall workflow to get what you're looking for would be:

1. Check whether your post has any blocks or not, using has_block function. has_block^Docs
2. If it does, then get all of the blocks (including gallery block) using parse_blocks function. parse_blocks^Docs
3. parse_blocks will return an array of all blocks used in your post, so loop through them and see which one is called "core/gallery".
4. "core/gallery" block has "attributes" and "ids" for each image you've added in the admin panel.
5. Once you get the "ids", you should be able to create your custom button and image links using wp_get_attachment_image_url function. wp_get_attachment_image_url^Docs

As a POC:

Please see the following code:

The EXPORTHOW mechanism is only for overriding the metaclass that will be used for package declarators, with the slight extension that EXPORTHOW::DECLARE also performs a grammar tweak that introduces a new package declarator.

While one can call .HOW on a Sub, the result does not relate to the subroutine itself, but rather the metaclass of the Sub type, of which a subroutine is an instance.

Really, EXPORTHOW is an "easy things easy" mechanism (to the degree it's fair to call anything relating to meta-programming easy!) It was also a straightforward thing to provide: the parsing of package declarations was already extremely regular, and the compiler already maintained a mapping table from package keyword to metaclass, so providing a way for a module to replace entries in that table (or add new ones for DECLARE) was barely a few hours of compiler hackery.

Routines are vastly less regular, even if that's only somewhat apparent syntactically. While packages pretty much parse the keyword (class, role, grammar, etc.) and what follows is the very same syntax and semantics for all of them (modulo roles permitting a signature), there are separate parse rules and semantics behind each of sub, method, macro, and rule. Their interaction with the overall compilation process is also rather more involved. The ongoing RakuAST effort is bringing a bit more order to that chaos, and ultimately - when coupled with slangs - will offer a way to introduce new sub-like constructs, as well as to give them semantics.

This could be achieved using CSS and flexbox styling if they are contained within the same container.

If flexbox isn't possible due to the layout, for example h3 tags in different containers and unable to apply flexbox styles, Id take a look at using:

https://github.com/liabru/jquery-match-height

Good question. It got me curious and made me dig into this WC_Admin_Notices class. And here's what I found out!

Well, before I talk about WC_Admin_Notices class, first let's talk about your first question!

"the notice doesn't appear"

Because when the woocommerce_order_status_changed hook fires there is no screen associated with it and it's not just notices, for example if you try to do a print_r and/or an echo they won't show anything either because there is no screen associated with that hook. The only way you could find out that you hit that hook is by using die function. In order to test this, you could do this:

I recommend to rewrite affected files by the files from clean/original Wordpress (be sure you using the same version of the WP)