How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
Forum rules
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
Always add your Laravel, Aimeos and PHP version as well as your environment (Linux/Mac/Win)
Spam and unrelated posts will be removed immediately!
How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
Laravel framework version: 9.36.4
Aimeos Laravel version: * 2022.07.2
PHP Version: 8.1.9
Environment: Linux
I have created a theme extension and selected it.
Every time I change a CSS or JS file in...
vendor/aimeos-themes/mytheme/themes/client/html/mytheme/*.css
The changes don't reflect on the frontend without doing composer up
How can you temporarily avoid the entire process of having to execute composer up every time and use the theme files directly from the extension?
I can edit the files directly in...
public/vendor/shop/themes/mytheme
But I don't want to accidentally overwrite them with composer up at a later point.
Aimeos Laravel version: * 2022.07.2
PHP Version: 8.1.9
Environment: Linux
I have created a theme extension and selected it.
Every time I change a CSS or JS file in...
vendor/aimeos-themes/mytheme/themes/client/html/mytheme/*.css
The changes don't reflect on the frontend without doing composer up
How can you temporarily avoid the entire process of having to execute composer up every time and use the theme files directly from the extension?
I can edit the files directly in...
public/vendor/shop/themes/mytheme
But I don't want to accidentally overwrite them with composer up at a later point.
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
You can link the ./packages/<extname>/themes/ folder of your extension to ./public/vendor/shop/themes/<extname>/ directory.
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
I'm sorry, how do you 'link' it
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
Use the Linux command line utility "ln":
https://linuxize.com/post/how-to-create ... n-command/
https://linuxize.com/post/how-to-create ... n-command/
Professional support and custom implementation are available at Aimeos.com
If you like Aimeos, give us a star
If you like Aimeos, give us a star
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
I tried the following links
ls - s ./packages/<extname>/themes ./public/vendor/shop/themes/<extname>
ln -s ./packages/<extname>/themes/client/html/<extname> ./public/vendor/shop/themes/<extname>
it keeps looking for the files in ./public/vendor/shop/themes/<extname>
ls - s ./packages/<extname>/themes ./public/vendor/shop/themes/<extname>
ln -s ./packages/<extname>/themes/client/html/<extname> ./public/vendor/shop/themes/<extname>
it keeps looking for the files in ./public/vendor/shop/themes/<extname>
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
I solved it by providing the full paths when linking:
And for removal of the link, the command is:
Should be noted that before linking to .../public/vendor/shop/themes/<extname>, the directory had to be deleted.
It will not link properly if the public theme directory already exists.
For listing of symbolic links to the directory, the command is:
Code: Select all
ln -s /var/www/vhosts/<domain>/httpdocs/packages/<extname>/themes/client/html/<extname> /var/www/vhosts/<domain>/httpdocs/public/vendor/shop/themes/<extname>
Code: Select all
unlink /var/www/vhosts/<domain>/httpdocs/public/vendor/shop/themes/<extname>
It will not link properly if the public theme directory already exists.
For listing of symbolic links to the directory, the command is:
Code: Select all
ls -l /var/www/vhosts/<domain>/httpdocs/public/vendor/shop/themes/<extname>
Re: How to avoid having to use "composer update" when changing CSS and JS files in my theme extension?
You saved my life!!!
Thank you so much!!
Thank you so much!!