Invalid file path – outside allowed directory

  • Resolved graymatter00

    (@graymatter00)


    3 weeks, 1 day ago

    I’m getting this error when FVM is activated, but not when it is deactivated.

    /* Error on https://shrinkwrap.blog/wp-content/plugins/cardoza-facebook-like-box/cardozafacebook.css : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/related-posts-by-taxonomy/includes/assets/css/styles.css : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/contextual-related-posts/includes/frontend/css/text-only.min.css?ver=4.2.4 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress/assets/css/unsemantic-grid.min.css?ver=3.6.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress/assets/css/style.min.css?ver=3.6.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress/assets/css/mobile.min.css?ver=3.6.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress/assets/css/components/font-icons.min.css?ver=3.6.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress/assets/css/components/font-awesome.min.css?ver=4.7 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/themes/generatepress-child/style.css?ver=1737596949 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/ajax-search-lite/css/style.basic.css?ver=4.14.4 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/ajax-search-lite/css/style-underline.css?ver=4.14.4 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/recent-posts-widget-with-thumbnails/public.css?ver=7.1.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/easy-customizable-text-widget/css/frontend.css?ver=28.07-17 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-content/plugins/gp-premium/blog/functions/css/featured-images.min.css?ver=2.5.6 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 : Invalid file path - outside allowed directory */ /* Error on https://shrinkwrap.blog/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1 : Invalid file path - outside allowed directory */

    WP and all plugins are updated. FVM settings…

    Screenshot_17-7-2026_122241_shrinkwrap.blog.jpeg

    • This topic was modified 3 weeks, 1 day ago by graymatter00.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Raul P.

    (@alignak)

    3 weeks, 1 day ago

    Hi,

    Which hosting are you using?

    I am guessing, your site is hosted in a way where the folder paths use “shortcuts” (symlinks) so it triggers a built-in safety check that makes sure it only reads your own website’s files (and nothing it shouldn’t).

    That safety check is maybe too strict for this type of situation, so I will adjust that on the next update.

    Once you see the update, purge all caches and try again, and it should be good to go.

    Thread Starter graymatter00

    (@graymatter00)

    3 weeks, 1 day ago

    Thanks for the quick response @alignak.

    We’re using SmarterASP.net hosting (SmarterASP.NET – Unlimited ASP.NET Web Hosting). We have a number of sites that are ASP.Net based, so we stuck with them for this WordPress site as well.

    I look forward to the update. Do you have an expected release date for it?

    Plugin Author Raul P.

    (@alignak)

    3 weeks, 1 day ago

    Should be up already. Thanks

    Thread Starter graymatter00

    (@graymatter00)

    3 weeks, 1 day ago

    @alignak Version 3.5.7 looks to have fixed it. Thanks! 😎

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.