← Back to Backend Skin Support
Awesome plugin! I would like to have an option that the skin of the backend this be of each theme but in its own theme. something like that:
* /themes
* /my-theme1
* /my-theme2
* /backend-theme
Do you think it can be made easy? And if i want
* /themes
/my-theme1
/my-theme2
* /backend-theme
i have designers with only access to theme
folder.
Last updated
This is good feature for the next version for the plugin. I will include to my list of feature for this plugin
Hi,
I already created a new version 1.1.0
for the Backend Skin Plugin.
Instead of using backend-theme
I use backend-skins
Also updated the documentation on how to use it.
Thank you for your update, but now not works fine.
The problem is with the file assets / css / october.css
the dev tool says ...
GET http: //localhost.loc/backendskins/default/assets/css/october.css? V446 net :: ERR_ABORTED 404 (Not Found)
The template recognizes it, but not that file.
What could be the problem?
Hi>gustavo.ar said:
Thank you for your update, but now not works fine. The problem is with the file
assets / css / october.css
the dev tool says ...GET http: //localhost.loc/backendskins/default/assets/css/october.css? V446 net :: ERR_ABORTED 404 (Not Found)
The template recognizes it, but not that file.
What could be the problem?
Upon checking this one, its not the plugin issue.
If you are using apache, you can do this. Add this to .htaccess
##
## White listed folders
##
...
RewriteCond %{REQUEST_FILENAME} !/themes/.*/(assets|resources)/.*
RewriteCond %{REQUEST_FILENAME} !/backendskins/.*/(assets|resources)/.*
...
I will update the document for this.
This plugin is great, and works perfect, the only thing I can add, I think it should work backendskins/default
without having to run a command by console, since in shared servers many times you do not have access.
Thank you
1-8 of 8