Title: fob's Replies | WordPress.org

---

# fob

  [  ](https://wordpress.org/support/users/fob/)

 *   [Profile](https://wordpress.org/support/users/fob/)
 *   [Topics Started](https://wordpress.org/support/users/fob/topics/)
 *   [Replies Created](https://wordpress.org/support/users/fob/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/fob/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/fob/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/fob/engagements/)
 *   [Favorites](https://wordpress.org/support/users/fob/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 1 through 15 (of 72 total)

1 [2](https://wordpress.org/support/users/fob/replies/page/2/?output_format=md) 
[3](https://wordpress.org/support/users/fob/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/fob/replies/page/4/?output_format=md)
[5](https://wordpress.org/support/users/fob/replies/page/5/?output_format=md) [→](https://wordpress.org/support/users/fob/replies/page/2/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Redirection] Critical errors with current update](https://wordpress.org/support/topic/critical-errors-with-current-update/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [4 months ago](https://wordpress.org/support/topic/critical-errors-with-current-update/#post-18775736)
 * Unfortunately, it seems that PHP-FPM + OPcache retain paths in memory, which 
   occasionally causes problems with updates these days (even if the code otherwise
   works flawlessly).
 * In plugins, the best way to address this issue may be to add a small piece of
   extra code like this:
 * /*
   if (function_exists(“opcache_reset”)) { opcache_reset(); }*/
 * On the server side, you can slightly adjust the PHP.ini on performance-optimized
   servers to have links in the server cache automatically checked the next time
   they are accessed:
 * /*
   opcache.validate_timestamps=1opcache.revalidate_freq=1realpath_cache_ttl=10*/
 * Because this can probably only cover about 90% of such caching errors, I now 
   run a bash script outside of business hours that checks where updates have taken
   place in order to automatically restart PHP there, which reliably refreshes all
   caches. 🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Redirection] Critical errors with current update](https://wordpress.org/support/topic/critical-errors-with-current-update/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [4 months, 1 week ago](https://wordpress.org/support/topic/critical-errors-with-current-update/#post-18773197)
 * I still had one attempt left in a test environment. It appears to be a more general
   caching issue in a PHP-FPM environment with an upstream NGINX cache that was 
   not updated promptly enough during the update.
 * It seems to be sufficient to update the plugin (with page failure error) and 
   simply restart PHP 8.3.x once immediately after the update.
 * I suspect that moving the file ‘redirection-version.php’, which is included via‘
   require_once’, to a subdirectory led to the incorrect search for this file.
 * PHP message: PHP Warning: require_once(/…/wp-content/plugins/redirection/redirection-
   version.php): Failed to open stream: No such file or directory in /…/wp-content/
   plugins/redirection/redirection.php on line 45
 * PHP Fatal error: Uncaught Error: Failed opening required “/../wp-content/plugins/
   redirection/redirection-version.php”
 * Do you think it might help to first define the paths and dependencies that need
   to be changed during plugin updates and then query and integrate them conditionally?
   Something like this?
 * // Define the path to the file
   $version_file = plugin_dir_path(FILE) . “new_subdirectory/
   redirection-version.php”;
 * // Check whether the file exists before integrating it
   if (file_exists($version_file)){
   require_once($version_file);} else {// Optional: Error handling or fallback}
 * Could something like this perhaps help a little to feed modern nested caching
   systems with fresh data in good time before they cause unexpected errors?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Redirection] Critical errors with current update](https://wordpress.org/support/topic/critical-errors-with-current-update/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [4 months, 1 week ago](https://wordpress.org/support/topic/critical-errors-with-current-update/#post-18773054)
 * It appears that in PHP 8.3, activating the updated plugin triggers an endless
   redirect loop, which is terminated on the server side and acknowledged with Error
   500. In PHP 7.4 environments, however, the plugin could be updated without any
   problems and without the error:
 * “Core Error / AH00124: Request exceeded the limit of XXX internal redirects due
   to probable configuration error. Use “LimitInternalRecursion” to increase the
   limit if necessary. Use “LogLevel debug” to get a backtrace.”
 * I haven’t looked at the code to see if it might be related to one of those annoying
   minor PHP updates or an ill-timed (perhaps complexer) activation loop?
 * [https://wordpress.stackexchange.com/questions/25910/uninstall-activate-deactivate-a-plugin-typical-features-how-to/25979#25979](https://wordpress.stackexchange.com/questions/25910/uninstall-activate-deactivate-a-plugin-typical-features-how-to/25979#25979)
 * [https://developer.wordpress.org/reference/functions/register_activation_hook/](https://developer.wordpress.org/reference/functions/register_activation_hook/)
    -  This reply was modified 4 months, 1 week ago by [fob](https://wordpress.org/support/users/fob/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Redirection] Critical errors with current update](https://wordpress.org/support/topic/critical-errors-with-current-update/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [4 months, 1 week ago](https://wordpress.org/support/topic/critical-errors-with-current-update/#post-18772819)
 * There was a problem with the reactivation process.
 * In PHP 8.3.28 the plugin could not be properly reinstalled after being updated
   from a Plesk Toolkit. Plesk activates the plugin, even if something does not 
   work. Then the affected websites go down. If you deactivate the plugin that caused
   issues, they run fine again.
 * If you tried to reactivate the plugn from the backend, to see what happens and
   track errors messages, it simply failed. (Activation not possible.)
 * So I tested it again with PHP 7.4 – works. Switched to PHP 8.3.x again – works.
 * As it stands, I have to downgrade the PHP versions everywhere, activate the update,
   and then switch back to the desired PHP environment. This way it seems to work
   fine. 🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WPCode - Insert Headers and Footers + Custom Code Snippets - WordPress Code Manager] Missing Header Links](https://wordpress.org/support/topic/missing-header-links/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [2 years, 9 months ago](https://wordpress.org/support/topic/missing-header-links/#post-16925135)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Bug with mobile views](https://wordpress.org/support/topic/bug-with-mobile-views/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [2 years, 12 months ago](https://wordpress.org/support/topic/bug-with-mobile-views/#post-16744853)
 * Fixed it with options (left menu). Whatever had happened there did not recur 
   afterwards.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Slide formatting lost + Server error 500](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/)
 *  [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/#post-16726529)
 * 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 3 years ago by [fob](https://wordpress.org/support/users/fob/).
    -  This reply was modified 3 years ago by [fob](https://wordpress.org/support/users/fob/).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Slide formatting lost + Server error 500](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/)
 *  [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/#post-16725625)
 * 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. 
   🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Feature Question](https://wordpress.org/support/topic/feature-question-17/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/feature-question-17/#post-16723365)
 * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Feature Question](https://wordpress.org/support/topic/feature-question-17/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/feature-question-17/#post-16718162)
 * Regarding the loading features, I can not see any difference. 🙁
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Feature Question](https://wordpress.org/support/topic/feature-question-17/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/feature-question-17/#post-16718157)
 * 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.
   🙂
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Slide formatting lost + Server error 500](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/)
 *  [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/#post-16715832)
 * 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.wordpress.org/log/depicter/](https://plugins.trac.wordpress.org/log/depicter/)
 * If the 1.7.3 version worked for you, you could get it from the advanced view 
   of the plugin page: [https://wordpress.org/plugins/depicter/advanced/](https://wordpress.org/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
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Slide formatting lost + Server error 500](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/)
 *  [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/slide-formatting-lost-server-error-500/#post-16714166)
 * 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:
 *     ```wp-block-code
       /**
        * 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.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Depicter — Popup & Slider Builder] Feature Question](https://wordpress.org/support/topic/feature-question-17/)
 *  Thread Starter [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years ago](https://wordpress.org/support/topic/feature-question-17/#post-16704819)
 * 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](https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading)
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Spam Protect for Contact Form 7] Mistake in class-front.php](https://wordpress.org/support/topic/mistake-in-class-front-php/)
 *  [fob](https://wordpress.org/support/users/fob/)
 * (@fob)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/mistake-in-class-front-php/#post-16367203)
 * +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.

Viewing 15 replies - 1 through 15 (of 72 total)

1 [2](https://wordpress.org/support/users/fob/replies/page/2/?output_format=md) 
[3](https://wordpress.org/support/users/fob/replies/page/3/?output_format=md) [4](https://wordpress.org/support/users/fob/replies/page/4/?output_format=md)
[5](https://wordpress.org/support/users/fob/replies/page/5/?output_format=md) [→](https://wordpress.org/support/users/fob/replies/page/2/?output_format=md)