fob

Thank you. I cleared the browser cache manually and tested with different browsers. If there are no limitations from the plugin, it must be a caching issue somewhere. As it is just a favicon problem (effecting apple users only, because the manifest for android works), I will check that tomorrow again.

Fixed it with options (left menu). Whatever had happened there did not recur afterwards.

Problem is, that plugin resources are loaded everywhere. This means, that all pages will load a little bit slower AND if there is a bug, you can find it everywhere (not only on slider pages). For example, I can see a console error in Chrome (incognito mode), on pages that can have no slider output because they do not have a slider installed. ??

DevTools failed to load source map: Could not load content for .../depicter/resources/scripts/player/depicter.js.map: HTTP-Fehler: Statuscode 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

Slider pages seem to work well for me, but log the same error.

• This reply was modified 1 year, 6 months ago by fob.
• This reply was modified 1 year, 6 months ago by fob.

Works. Had some issues after updating to the latest version.

• Sliders had to be published again
• Sliders were gone on some pages (“no content yet” was shown for normal visitors / non admins)
• Updating pages fixed those issues (confirming sliders on page and saving the page again).

Would like to remove style and image preloads (for sliders below the fold) but have been able to improve speed with caching/dependency managers for now. Happy to have found “alt tags” (image descriptions) in the code (for images that have descriptions in media uploads).

I have been unsure yesterday, if I have some kind of new trouble with sliders that were invisible on certain pages after updating those pages. Might have been a problem with server caching. Today everything seems to work fast and fine. ??

I am already using a caching/dependency manager to delay the slider (script) until the user scrolls. I also tried to remove your preload filter (“depicter_add_preload_to_styles” function) in theme functions.

For me it would be nice enough to get a simple hook that gives me possibilities to filter preloading settings in wp_head, where it is not necessary to load two additional stylesheets for one player on every page (for example).

Currently I can only catch “depicter-front-pre-css” to be loaded as preferred (asynchronously) but the two additional player scripts (per page) can not be moved to (normal) loads as well.

Images are preloaded only for the first slide now, with media width controls (better than before).

So – the latest bug and security fix (1.9.2) make things a little bit better for me, but isn’t perfect right now.

Thanks for the good work.

Regarding the loading features, I can not see any difference. ??

Thank you very much for your helpful answer.

I can confirm now, that images have an alt tag, if designers had not changed the images without descriptions behind my back, ignoring all my warnings that they must never upload images without useful descriptions. This is good news. When I was checking the code (just for the first slider picture, sorry for that), I just saw something like * alt=”OX!B%h7KnpfSVhPt” * – but elder uploads still have my examples (for designers). I will talk to them tomorrow! ??

Regarding the preloads the situation is as follows:

I do not want sliders to start above the fold because of the heavy weight (scripts, styles and pictures). I place them somewhere else to load later. CSS will be loaded asynchronously in this configuration and slider scripts are loaded after user interaction, not earlier. This is why I would like to have no preloads for slider images, too. I need to load the logo, some text and one image (only) as fast as possible.

What I can see is, that depicter preloads three versions of the first slider picture and two stylesheets. It would be great to have an easy option to avoid all preloads.

Thank you for explaining loading features a bit more understandable. I will definitely have a look at the “Load nearby slides feature”. Perhaps it helps, to improve performance a little bit more. Great, if that option enables what I was looking for. I think the loading features could be better described somewhere, if so. ??

I am sorry to learn that the solution did not help you. Perhaps a typo mistake in that line that checks, if there are arrays that can be merged? A bracket loss or something?

I was testing the slider these days with good and bad results, but for the given purpose better than others. In case nothing works for you with the latest version, you could try to install the version before and see if it helps. Versions seem to have jumped from 1.73 to 1.9.0 (the buggy version): https://plugins.trac.www.ads-software.com/log/depicter/

If the 1.7.3 version worked for you, you could get it from the advanced view of the plugin page: https://www.ads-software.com/plugins/depicter/advanced/ and downgrade (roll back to 1.73) for a while.

I also had some trouble with the new version. I had to train the firewall (against conflicts with the editor), had to renew sliders several times, sometimes from the depicter dashboard, sometimes on the post (page dashboard) to make them available again, … suddenly the bug came up and wanted to have that fix to hide the system from trying to merge arrays that seem not to exist. For me it currently works with the given sliders. Good luck to you.

If clients insist on sliders you have to compare and find something that fits best. Depicter does not need jQuery anymore to work. That is a big plus (for me) against other sliders in modern systems. Unfortunately, it does not support lazy loading (bad for speed on the other hand, as it loads the pics before you need them). It also does not support explaining descriptions (alt tags). Another great plus is the “jump in, scroll fast, stop where you want” feature for slides.

In recent testings I found the Gutentor Slider to be number 2 on the list. It supports everything you need (from the SEO perspective) but needs jQuery to work without console errors. Perhaps you want to give it a try as an alternative slider tool with nice Gutenberg Editor Features, if your system still requires jQuery and have no plans to change that. It also uses adaptive images, supports lazy loads, alt tags and Gutenberg Editor Options.

Best regards,

Oliver

Quick and dirty I fixed it before the array_merge so that the client can play with slides and pages again until a bug fix comes:

/**
 * Merges the defined arguments into defaults array.
 *
 * @param array|object $args    Value to merge with $defaults.
 * @param array $defaults        Array that serves as the defaults.
 *
 * @return array
 */

public static function merge( $args, $defaults = [] ) {
	if ( is_object( $args ) ) {
		$args = get_object_vars( $args );
		}

	if ( is_array( $defaults ) && $defaults && is_array( $args ) && $args ) {
	return array_merge( $defaults, $args );
	}

	return $args;
}

/wp-content/plugins/depicter/vendor/averta/core/src/Utility/Arr.php

Line 24-59, modified only line 74 to stop running into problems with line 75. Perhaps it helps you, too.

Hi. Thank you for your response.

I just double-checked if we are talking about the same thing. While you seem to be talking about rearranging images (while loading one by one) I thought about a performance feature in the website loading process. “Lazyloading” is for browsers (and Google Lighthouse checks), to inform them that you load only the things needed while loading the website. So – if it would be possible to use a tag like *** loading=”lazy” *** for images that do not have to be loaded before reading, that might be excellent to improve the good performance a little bit more. (First image should be loaded without the tag, if loaded early (at the top of the website).

Here you find some more information regarding the critical parts of loading: https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading

+1

Good idea, not to remove empty spaces between words in phrases. The original code was empty on both ends of the function (no comma). It did not separate the spam words, but combined them to a new word. Should be better and enough to clean the phrases on both end points instead.

Thank you for the detailed answer.

I found an option to additionally allow post formats for search engines in Yoast SEO that seem to have resolved some of the issues.

Regarding the structured data I would like to suggest comparing the things with Google views. They want you to promote nothing in the JSON part of a page that can not be seen by a real user. Crawlers should be able to find a match.

I appreciate your thoughts and understand the update effort quite well. Thanks a lot.

New version 3.3.6 works great.

Thanks very much.

Thank you for asking. The site is using the standard function “yoast_breadcrumb()” like this: “yoast_breadcrumb(‘<div class=”the-bc-class”>’, ‘</div>’). Yoast admin configurations, no additional filters in form of functions for filtering the visual output of breadcrumbs on posts, archives or pages.