I am using a drupal community theme, slightly customized as per requirement. I am facing problems when I am porting the theme with a distribution.
On installation that distribution does not load the custom theme, but downloads the theme from drupal community.
Please help.
Don't use Drush for that because Drush will fetch the files (modules, themes etc) from the online repositories.
Just follow the normal installation method. Download the installation profile, override the theme folder with your customized theme folder and then run the install.php through browser.
Related
I use pip to install wagtail on my computer. Its operating system is windows 10. In my project, I need to customise the admin UI, mainly to modify the css file in client folder. The folder client is peer to folder wagtai on github. But I can not find the client folder on my computer.
How to find the client folder?
Wish for your help.
The client folder is not part of the installed Wagtail package - instead, the package contains compiled and minified versions of the CSS and JavaScript assets as part of the Django apps that make up Wagtail, for example under wagtail/admin/static/wagtailadmin/css/. This is because Wagtail's stylesheets are written in Sass and need to be compiled using a Node / NPM-based toolchain to be usable in the browser, and end users of Wagtail aren't expected to have this toolchain installed.
As a result, making arbitrary customisations to Wagtail's CSS isn't formally supported - to do it, you'll need to start from a checkout from Github, and set up a dev environment as per the documentation. As of Wagtail 2.12 it is possible to customise the colour scheme using CSS variables, though.
In Drupal7, besides updating theme from admin which requires FTP, can I just rename the old theme folder and drop in the new version theme folder?
Best way would be following the below steps:
Firstly uninstall the theme
Then remove the folder
And then upload the new theme
And finally enable the theme.
Note: dont forget to keep the old theme folder as a backup before replacing it with new theme, just in case some css, images or js can break your site
I have multiple ExtJS apps based on a custom theme say "my-ux-theme" (extension of "ext-theme-crisp").
I have bunch of .SCSS files repeated in each one of the apps. Every time I make any change to the theme, I have to make change in each of the SCSS files across the apps.
I want to centralize my theme
I am planning to attach "my-ux-theme" to the KitchenSink application and then I am building the entire KitchenSink which produces the .CSS files I need. I then deploy this CSS to my CDN and linking all my apps to this theme (CSS files). Is this a good approach?
Is this a safe assumption that KitchenSink is a big app covering all the components in ExtJS and is generating all the CSS I would ever need?
Can you all please suggest?
The basic question is when we do Sencha Command on an ExtJS application (sencha app build) then the generated CSS files by the theme covers only those components which are used/present in the application? Or it doesn't matter?
Using Kitchen Sink does not feel right to me, Here is what you can do.
Create a Sencha Work Space
Create a Theme Package
Build the Theme Package using "sencha package build"
It will generate one single CSS file for your theme in build/resource/theme-name-all.css
Here are commands for it
sencha -sdk {path/to/Ext-JS-5-SDK} generate workspace my-workspace
sencha generate package -type theme my-custom-theme
sencha package build
I used Sencha Cmd to generate workspace, app, package, custom theme, and edited my custom theme package.json to extend ext-theme-gray.
But when I refresh the app and build the package, my app does not reflect the gray theme.
I should mention that the ExtJS 4.2 docs on themes mentions the standard theme folders should be in my workspace packages folder by now, but they were not, though I followed the instructions to generate workspace/package exactly.
So I copied the ext-theme-gray folder to my packages folder and then did app refresh and package build.
But my UI still does not reflect the gray theme.
Am I missing something?
I needed to specify the custom theme here:
extApps/usx/.sencha/app/sencha.cfg
You have to specify your new/custom theme on your project's config file found on .sencha/app/sencha.cfg.
app.theme=my-custom-theme
#app.theme=ext-theme-classic
Then execute sencha app refresh from your project's root directory.
The theming guide says to run Sencha Cmd to:
- setup the workspace
- generate a test app to test the custom theme
The test app created in the theming guide is located inside the workspace folder. My question is, does the app that will use the theme need to be located inside the workspace folder? Or can it reside elsewhere, and it simply uses the built custom theme?
We have an existing app that we now want to use a custom theme, so the app is not inside a workspace. Can I just create the workspace for the custom theme, and make changes for styling necessary to implement the theme? Do I need to make configuration changes in the generated workspace so it is aware of the location of the code for the app which is not in the workspace?
Thanks in advance!
As far as I know, your project, where you wanted to apply the theme, must be generated by Sencha CMD. After generating the project, copy everything from the existing project to the new sencha cmd-generated project.
On the terminal, execute sencha generate theme my-custom-theme on the application directory. Your my-custom-theme will be created on the packages directory of your project folder. In order to use this theme, edit sencha.cfg found on the [project folder]/.sencha/app/. Change the app-theme to app.theme=my-custom-theme.
In order for the changes to take effect, execute sencha app refresh.
The theme, i.e. .scss files, eventually converted into a CSS file. You need to include this generated CSS file in your index.html. This is regardless of how you get or generate the CSS file.
I do not think your existing project need to be inside your new 4.2 theme project. However, it is much easier to test if you are creating a new theme and they reside in the same project.
It is not difficult to put your existing .js files into 4.2 project. I had to replace the app directory from the old project and some update to files. You can find the details in the ExtJS upgrade guide.
In the new Sencha Architect 3, there's an added feature of Application Styling. See here: http://docs.sencha.com/architect/3/#!/guide/styling
I'm not sure but I think you can import your current ExtJS project into the Architect and start styling your application.