galleries | module used to be available for PyroCMS | Widget library

There's a working example here:

https://github.com/bobdenotter/phpnews_2019/blob/master/src/RssFetcherExtension.php#L93-L191

I don't think the functions.php file has anything to do with it - usually HTML structures like this are created in template php files which are in the themes folder - either on the top level of that folder or as "template parts" in an according subfolder. You have to edit those( or actually those among them that are used by the pages you are referring to), changing all

However, since any not-selfmade theme will be updated every now and then, those changes would be overwritten with updated files when available, it would be necessary to create a child theme, which only contains those templates which you want to change (see also https://developer.wordpress.org/themes/advanced-topics/child-themes/). Then again, updated themes might contain template updates which are necessary, so you'd always have to check which details were updated in that particular template file, integrating it into your child theme templates or editing the updated original themes and using them in your child theme.

P.S.: I think the title of your question is a bit misleading: In the question text you are asking about certain title tags in the product pages, not about parts of the menu, aren't you?

This is not related to WordPress. It's related to either Apache or Nginx using the HTTP/2 standard.

REFUSED_STREAM (0x7): The endpoint refused the stream prior to performing any application processing (see Section 8.1.4 for details).

It can either come from too many concurrent streams:

Endpoints MUST NOT exceed the limit set by their peer. An endpoint that receives a HEADERS frame that causes its advertised concurrent stream limit to be exceeded MUST treat this as a stream error (Section 5.4.2) of type PROTOCOL_ERROR or REFUSED_STREAM. The choice of error code determines whether the endpoint wishes to enable automatic retry (see Section 8.1.4) for details).

It can also be sent during a Push Response operation:

If the client determines, for any reason, that it does not wish to receive the pushed response from the server or if the server takes too long to begin sending the promised response, the client can send a RST_STREAM frame, using either the CANCEL or REFUSED_STREAM code and referencing the pushed stream's identifier.

Or if the client is trying to connect using HTTP/1.1:

Servers that don’t wish to process the HTTP/1.1 response should reject stream 1 with a REFUSED_STREAM error code immediately after sending the connection preface to encourage the client to retry the request over the upgraded HTTP/2 connection.

There is no way for me to pinpoint what is happening during those requests, as it can have multiple reasons, as stated above.

So I suggest you a couple of options:

• Pass your site's traffic throughugh Cloudflare, so they act as a middle-man for these connections and normalize the requests sent to your server
• You can increase the SETTINGS_MAX_CONCURRENT_STREAMS to minimize the risk of sending a REFUSED_STREAM. If you use Nginx, you can see how to do this here: http://nginx.org/en/docs/http/ngx_http_v2_module.html#http2_max_concurrent_streams
• If you don't know how to do the above, contact your hosting company and ask them to do it for you and upgrade your Nginx version, as some older versions are known to have issues.
• Disable HTTP/2 in Nginx. How to disable http2 in nginx
• As a last resource, you can migrate to another hosting company.

If you use Apache, everything I said above applies to it as well.

First install this into your python

pip install PyMuPDF Pillow

pip install fpdf

After this we extract the images with the below code.

Here's a working JSFiddle. Here's what I did, working through the installation page I referenced yesterday:

1. Starting in the "Include CSS and Javascript files" section, they say to include lightgallery.css, though they don't give a link for it. I searched and found a CDN link, and added that ;

2. Added a CDN link to the latest jQuery;

3. Copied and added the 'jsdelivr collection' link for the Lightgallery JS;

4. Copied the JS they show to initiate the plugin;

5. Copied the relevant part of your HTML snippet - just the lightgallery div, with some minor updates:

   • Neither video-poster1.jpg nor img/thumb1.jpg exist here of course, so I replaced them with placeholder images;
   • I get "Video unavailable" for that video, so I randomly picked another;

This works fine - the placeholder thumbnail is shown, when I click it the video opens against a black background, and plays if I click play. Here's the code:

is there a common convention when it comes to this problem ?

The important thing to recognize is that DELETE and PUT are of the transfer of documents over a network domain.

We use the standard methods in standard ways so that general purpose components can understand what the messages mean and do intelligent things.

If the semantics of the request are "the target uri should answer GET requests with a 404", then DELETE is appropriate. The underlying details of how your implementation achieves this are irrelevant.

Note that the definition of DELETE is pretty explicit about the limits of the semantics

If the target resource has one or more current representations, they might or might not be destroyed by the origin server, and the associated storage might or might not be reclaimed, depending entirely on the nature of the resource and its implementation by the origin server (which are beyond the scope of this specification).

Where things get really messy: HTTP gives us agreement on the meaning of the semantics of messages, but does not restrict implementations. In particular, it is perfectly valid that a DELETE of one resource would also change the representation of some other resource, or vice versa.

Imagine, if you will, that the gallery is a web page (/gallery/1/photos/webpage.html), with links to images, including a link to /gallery/1/photos/3.

id have to be uniq to avoid problem..

eliminate id="big" and replace id="thumbnails" by class="thumbnails"

Wordpress permalinks are pretty sensitive, do your due diligence before pushing to live.

You don not need to change the permalink in the settings, leave it to /%postname%/.

In your function.php, let's add the following just to make that when we mess with the permalinks they actually updates.

You can get the user who has last modified the file by using another action which I have specified in the image below

Flow action

Hope this has solved your question

Regards
RT