RuntimeException thrown – not a valid MVC template

  • Resolved mpp32

    (@mpp32)


    8 years, 9 months ago

    RuntimeException thrown
    (full server name and path…) \wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\nextgen_addgallery_page\templates\upload_images.php is not a valid MVC template

    I have been frustrated by this problem for over a week and probably read every forum out there. Although I’ve seen similar postings re. “the not valid MVC template”, mine seems to be a bit different. At first, I thought this was a migration issue, but now it seems that it is not.

    Yes, I’m using a Windows hosting server. It’s IIS 7.5 which is apparently the most compatible with php and often used for wordpress. It’s running php 5.6, my wordpress is 4.5.2 and NextGen gallery Version 2.1.43.

    I developed a complete wordpress site with several NextGen galleries locally on my Windows PC using Wampserver3 and everything worked as intended. When I migrated to the live Windows webserver “correctly”, I could not go to any page that contained a NextGen gallery as I would get a similar Runtime Exception thrown with reference to the full server name along with the “\nextgen_addgallery_page\templates\ <file>.php is not a valid MVC template”. Furthermore, I could not add a gallery, I could not get into the Gallery Settings or Other Options. At each attempt I got the Runtime Exception. I could not even Customise my theme because when I clicked, I got…

    “Edit Add NextGEN Media RSS
    NextGEN Media RSS

    RuntimeException thrown

    (full path)\wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\widget\templates\form_mediarss.php is not a valid MVC template”

    By the way, in the error message, the server path name (or UNC name) is missing the 2 leading backslashes (a possible clue?)

    When I deactivated and deleted NextGen, I could only then customise my theme without error. Since I could not get at the reset tool within settings, I download the stand-alone reset plugin – but that did not change anything. I then installed the previous version of NextGen (2.1.31), but that also made no difference.

    I then deleted all my wordpress files on the server and deleted the database, followed by a fresh plain install of wordpress and fresh new database. After confirming all was good, I did not add any themes or any other plugin, I only installed NextGen. However, again, I cannot add a gallery, cannot go into gallery settings, cannot go into other options and I cannot customize my theme. I tried with Twenty Sixteen, Fifteen and Fourteen. I even installed the Reset tool again just in case and ran it – no difference. I contacted my hosting provider and got them to make sure all appropriate permissions were set on my web space along with writable folders. All other themes and plugins work fine, the only exception is NextGen. Again, I cannot customise any theme unless I remove NextGen from my site.

    It seemed to me that NextGen was the best image gallery plugin for my needs and after investing so much time into this I really don’t want to move on to a different solution. So I hope I can get some help in resolving this – thanks!

    https://www.ads-software.com/plugins/nextgen-gallery/

Viewing 5 replies - 16 through 20 (of 20 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @hfdjb – Thanks for the update!

    – Cais.

    I experienced the same problem and the issue was the name path exceeded the number of characters allowed. I looked at reducing the number of characters for the upload/paste then went back and renamed the shortened folder names so the program worked as expected, this solved my issue.

    Here is an example of your text paths. Photocrati in the interest of documenting their program adds folders like ‘photocrati_nextgen’ that is part of the path but only contains the name of the next folder, yet helps to cause the problem with long paths.

    RuntimeException thrown
    (full server name and path…) \wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules

    \nextgen_addgallery_page\templates\upload_images.php is not a valid MVC template

    123 Words
    \wp-content\plugins\nextgen-gallery\products\photocrati_nextgen\modules\nextgen_addgallery_page\templates

    \upload_images.php

    106 words temporally remove ‘hotocrati_nextgen’
    \wp-content\plugins\nextgen-gallery\products\p\modules\nextgen_addgallery_page\templates\upload_images.php

    84 words temporally remove ‘extgen_addgallery_page’
    \wp-content\plugins\nextgen-gallery\products\p\modules\n\templates\upload_images.php

    Plugin Contributor photocrati

    (@photocrati)

    @purplepix – Thanks for sharing your findings … although I think it would be more correct to reference the number of characters in the path (which can be seen as a limitation within the server environment itself).

    – Cais.

    Cais, I am working on my computer off line with InstantWP making a tool for other club members. I did see that there is a limit for filename paths (just over 200). I tried different work arounds with out success. It wasn’t till I shortened the path name that I was able to copy and past the file(s). Once the files had loaded to the correct locations, it only required that I go back and rename the files I had shortened so that:
    \wp-content\plugins\nextgen-gallery\products\p\modules\n\templates\upload_images.php
    now became:
    \wp-content\plugins\nextgengallery\products\photocrati_nextgen\modules\nextgen_addgallery_page\templates\upload_images.php

    From the examples I used earlier, meaning it is a software limit issue that causes the problem. You are possibly using Linux and I don’t think it has the limit issue. Just trying to offer a simple solution to a complex problem.

    Plugin Contributor photocrati

    (@photocrati)

    @purplepix – We do appreciate your efforts to help. You are describing a limitation where you note the length of the path is the problem; we do not limit that within our code although it is a good troubleshooting tip to consider for those users experiencing similar issues.

    We don’t test with “InstantWP” and as you noted you are seeing that limitation, have you asked if it can be addressed within the environment it is creating?

    Thanks!

    – Cais.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘RuntimeException thrown – not a valid MVC template’ is closed to new replies.