MissingPluginException

[Andre Santiago]

I have created the theme as instructed, but when I install it, it is not visible by the system. It displays the following error:

2016-06-03 01:53:59 Error: [Cake\Core\Exception\MissingPluginException] Plugin MyTheme could not be found.

Path to the newly installed theme is not being detected. 

[Chris]

Hi,

I've just tried installing "BasicTheme" and seems to works ok. So I think your theme's "composer.json" may be incorrectly formatted.

Remeber:

- Themes are just CakePHP plugins

- If want to create a theme named  "Green" then you must create a plugin named "GreenTheme" ("Theme" word is the suffix used to indicate it should be treated as a theme instead of a plugin)

- So, if your package is named "MyTheme", you are telling to QACMS that you have a theme named "My". And in your theme's "composer.json" file you must use this as package "name": "VENDOR-NAME/my-theme"

Look the zip attached to this message, I've downloaded the original "BasicTheme" and changed its name to "MyTheme".

PS: I think we could bring back the "Theme Builder" shell from v1.x to to v2.x in order to make this process more simple.

Regards!

[Andre Santiago]

Chris,

There is something probably wrong with my setup. I tried the ThemeExample.zip you attached here, but I still get the same issue (See attach).

When I check the file at /vendor/cakephp-plugins.php, I don't see an entry for MyTheme. However, after I run

composer dump-autoload

, it shows up, but the system still says it cannot find it.

And on this file /vendor/composer/autoload-psr4.php, I have no entry for MyTheme. Also QA is uploading the theme to /plugins instead of /vendor/quickapps-themes... is that the desired outcome?

I think my next approach is to start from scratch and review this process in more detail. I will provide you more feedback.

Thanks

Andre 

[Christopher Castro]

Hi,

All plugins and themes installed using QA's backend are placed at ROOT/plugins, that is the expected behavior.

Try to active debug mode and see what is going on. But for what you've described seems to be a problem with QA's caches, you can try to clean all files under ROOT/tmp directory. Also check that `ROOT/tmp` has proper writing permissions.

Regards!

--
You received this message because you are subscribed to the Google Groups "QuickApps CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quickapps-cm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Christopher Castro.
I.T. Engineer. Senior Web Developer.
Pamplona, Spain
QuickApps CMS

[Andre Santiago]

Chris,

I cleared cache and enabled debug, please see attachment of the error.

Thanks,

Andre S.

[Andre Santiago]

Chris,

After debugging this file /vendor/quickapps-plugins/cms/config/bootstrap-site.php, I found that the failure was because the Theme's status was 0. As soon as I accessed the Database and manually switched the status for the pluginTheme to 1, the CMS was able to see the Theme and it started working as expected.

thanks,

Andre S

[Christopher Castro]

Hi,

I finally was able to reproduce the issue, but it actually occurs when you try to "Activate" the installed theme.

When themes are installed they're disabled by default (status = 0). Status changes to 1 only when you "Activate" them... So I think the problem is that QACMS for some reason is failing to change theme status when activating them.

Thanks for reporting!

--

You received this message because you are subscribed to the Google Groups "QuickApps CMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quickapps-cm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andre Santiago]

You are absolutely right Chris. Thanks for looking into it!