How do I get addons/my_changes to work ?

Developers Frontend
21

The ‘admin.php&cc’ command to clear the cache doesn’t work 100% on some servers.



Simply clear the cache (delete the files) manually through FTP or your hosting panel.



Delete all files and folders in:



/var/cache/

/var/compiled/

22

[quote name=‘indy0077’]The ‘admin.php&cc’ command to clear the cache doesn’t work 100% on some servers.



Simply clear the cache (delete the files) manually through FTP or your hosting panel.



Delete all files and folders in:



/var/cache/

/var/compiled/[/QUOTE]



Thanks indy, I’ve just tried that, deleted all files & folders as suggested…sorry to say, but still no change.



This line in styles.post.tpl is correct…isn’t it:



Is there anything different in 2.1.1 and are all the documents & references relevant to to this version?

What should the permission be for hooks/index? - currently it is : 755 and file permission for styles.css & styles.post.tpl is set to: 644.
23

[quote name=‘sellon’]What should the permission be for hooks/index? - currently it is : 755 and file permission for styles.css & styles.post.tpl is set to: 644.[/quote]

The permissions are right…

24

Ok, found!!:smiley:



My mistake, I was putting styles.css under /index folder.

25

Please post the contents of your:

skins//customer/addons/my_changes/hooks/index/styles.post.tpl

file surrounded in code tags using square brackets. I.e. [“code”] and [/“code”] without the quotes.



Also, if you could provide (or indicate) whether you are seeing the “link” tag for the css in your page source.



An additional way to diagnose this is to put

{debug}

at the top of your styles.post.tpl file. If the file is incorporated into the page flow then you will see a debug window pop-up.

26

Let’s say you wanted to add some new css in a file called new_style.css

try this:


  1. in the [COLOR=Blue]\addons\my_changes[/COLOR] directory (if it does not exist, create it) create a file called addon.xml with the following content:




my_changes
My changes
1
0
active

2) in the [COLOR=Blue]\skins[B]name-of-your-skin-here[/B]\customer\addons\my_changes[/COLOR] directory (if it does not exist, create it) create the following subfolders (if they do not already exist):



[COLOR=Blue]\skins[B]name-of-your-skin-here[/B]\customer\addons\my_changes\hooks[/COLOR]

and

[COLOR=Blue]\skins[B]name-of-your-skin-here[/B]\customer\addons\my_changes\hooks\index[/COLOR]





3) in the [COLOR=Blue]\skins[B]name-of-your-skin-here[/B]\customer\addons\my_changes[/COLOR] directory, place your new_style.css file





4) in the [COLOR=Blue]\skins[B]name-of-your-skin-here[/B]\customer\addons\my_changes[/COLOR][COLOR=Blue]\hooks\index[/COLOR] directory, create a file called styles.post.tpl file, with the following content:



5) in the admin panel, go to Administration → Addons and ake sure that My Changes is installed and Active





That’s all I had to do to get going with things (after learning how to clear the cache that is).



Good luck

27

[quote name=‘lekristine’ timestamp=‘1281993599’ post=‘86719’]

I had the same problem as brent’s. It was confusing to a rookie. This is what I found. To avoid any confusion …





First of all, depending on the scope you want to change there would be two my_changes directories:


  1. [web_site]\addons\my_changes\


  2. \skins[skin_name]\customer\addons\my_changes.





    The first one exists by default regardless the installation of the My Change addon in admin. It has addon.xml.





    However, the second one does not exist until you create it as tuari stated. Follow the steps below.




  1. Go to admin/addons/ - uninstall and install My Changes (this will delete all files and directories under 2) skin[skin_name]\customer\addons\my_changes, so back up any if you want to keep. If this is the first time it is ok since it does not exist yet.)




  2. Create the following directories:


  • \skins[skin_name]\customer\addons\my_changes


  • \skins[skin_name]\customer\addons\my_changes\hooks


  • \skins[skin_name]\customer\addons\my_changes\hooks\index




  1. Create and save tpl and css files appropriately




  2. Clear cache using ?cc


  • \admin.php?cc


  • \index.php?cc





    Note: In my case \index.php&cc gives an error, but index.php?cc works. I am not sure why. If someone has different experience or know why, I apprecaite your post.





    I hope this helps rookies :)

    [/quote]



    Ok, so I just tried this in the newest version of CS cart and it when I clicked the uninstall button, it deleted the entire addons directory and apparently our host doesn’t make backups.



    I have managed to restore most of the addons to our cart, but I am missing the my_changes addon from all packages I have.



    Where can I get it?



    How can I fix this awful mistake?



    Has no one tested this method on the new version of CS cart?
28

Has nothing to do with testing. When any addon is uninstalled, the skins for the addon are removed.

When an addon is “installed”, the var/skins_repository version of the addon is put in the skins directory.



So if you want to uninstall the my_changes addon, you should have ensured that you have it copied to the skins_repository.



Why would you uninstall the my_changes addon?