JA Sugite unable to update with JA Extension Manager

seanmcel

Hi
We are trying to update our JA Sugite template to the latest version, have purchased the one year pack but are unable to do so using JA Extension Manager, please see attached screenshots. Any help much appreciated, thank you.

saguaros

Hi seanmcel

There seems to be issue with update server of this template. I've reported to the team for further checking.

Kindly wait.

seanmcel

Ok thanks.

saguaros

seanmcel Thanks for your understanding!

seanmcel

Any more news on this please? We are keen to get this template updated and make some changes.

saguaros

Hi seanmcel

Unfortunately, there is an expected issue with the update of this template specific, the team is working on it.

At this moment, pls try to install template directly into your site:
-Take a backup of your site first
-Download latest version of template
-Go to Administrator panel of your site > Extensions > Install and install the downloaded package

If there is any issue, pls let me know.

We're sorry for any inconvenience it may cause.

seanmcel

Hi - wasn't I using the JA Extensions Manager precisely to avoid the problems of just installing the template directly in the usual way (ie. potential overwriting of core files). I don't understand why it is ok to do this now but it wasn't before?

I don't want to risk breaking my site doing it this way. Please let me know how long this will be and add this time on to my one year package as I am unable to use the template until you fix this issue.

saguaros

Hi seanmcel

It looks like that there is issue with the latest version of JAEM component 2.6.5 when checking the old version of this template (as the version you're using on your site).

Please try to use use the 2.6.4 version by going to download section: https://www.joomlart.com/member/downloads/joomlart/joomla-templates/ja-sugite

Download the version 2.6.4 of JAEM and install into your site:

Then you can check and update JA Sugite template.

We're still working on fixing the issue with the version 2.6.5. I will keep you posted.

Regards

seanmcel

Ok thank you, now we are making progress. 🙂

I have installed JAEM 2.6.4 and that appears to be working now. When checking the file comparison between ja_sugite version 1.1.0 and 2.0.1, there is quite a lot of variation (conflicted files and files modified by user) so I'm not quite sure how to proceed (these files would have been modified by an external developer). For example, in the attached screenshots, I'm not sure if I should replace these changes line by line (it's complicated as many of the lines don't correspond exactly and I wouldn't be confident of putting the line items in the correct place) or take a backup of the current conflicted and modified files, then use these to overwrite the new files of the same name when the template is updated.

If I backup the current files and overwrite the updated ones though, there are two issues. Any important updates to these particular files will not find their way to my website and secondly, when the next general update of the template is issued, they will be overwritten again won't they?

Can you tell me the best way to proceed please?

saguaros

Hi seanmcel

I recommend you to backup current conflicted + modified files, then overwrite the new files after template is updated. Especially for the file like 'templateDetails.xml' - this file relates to the version management of template so you should do this way.

For other files that you modified in template, in the future, you should put your override files into the local folder of template as we suggested here: http://www.t3-framework.org/documentation/extend-com-content#isolate-template so that these files will not be affected by the new update of template.

Regards

seanmcel

OK, I have made a list of all the conflicted and modified files. I will download these to my desktop.

If I then upload these files to the 'local' folder after updating the template, will this be enough? Or do I need to both upload them to the local folder and also overwrite the same new files in the main folder also?

If the second option, does this mean that every time I update the template, I will need to go through all of this process each time?

saguaros

Hi seanmcel

With 'local' folder, what I meant is that:

1 - This local folder helps keep your customization on template like layouts/style...
2 - When you update new version of template, all files in this 'local' folder will not be affected as the new version will overwrite the default files/folders come with template only. (Another file that will not be affected is /css/custom.css file)

So if you customize code in local folder, when you update, your customization will not be lost. At this moment, if you don't use 'local' folder and you already made custom changes in based files/folders of template, you can compare files via JAEM component and backup your changed files and apply again to the updated files.

I hope this makes senses.

seanmcel

OK - so the local folder is the preferred folder then and will take preference over any folder or file of the same name that is currently in the default files/folders?

What I'm trying to get my head around is that if I put these conflicted and modified files into a local folder, they will also be in the default folders also - correct? So when I update the template, will the local files/folders take preference over the default files/folders? Will the system load the local folders first instead of the default ones?

saguaros

Hi seanmcel

Let me take an example, if you override login module in local folder:

/templates/ja_template/local/html/mod_login/

This folder will be used in priority on frontend, if this login module is not overridden in local folder, the folder in template will be used:

/templates/ja_template/html/mod_login/

When you compare in JAEM, JAEM will compare files in new version vs files in existing version your site is using, not the files in local folder. So, basically, when you customize this login module and put changes inside local folder, it will not be affected when you update new version of template. That's initial idea of using local folder in template.

I hope this makes senses.

seanmcel

Ok great, thank you for clarifying.

seanmcel

I have started the process of copying the conflicted and modified files over to the local folder using Filezilla. In the local html folder, there were several folders that were on the website but that not exist so I have created them. These are folders such as com_content, com_contact, com_easyblog etc.

There were several files marked in green which were new files 'created by user'. So I downloaded these also and copied them into the local folders.

I have just checked now and my site is down. I am only about halfway through the process of moving the downloaded files into the local folder - have I done something wrong here?

As my site is now down, I'd appreciate a reply asap please! Thank you!

seanmcel

I'm just wondering if I should be copying all these com and mod directories? For example, html/com_easyblog/blogs/latest, html/mod_j2store_currency, html/plugins/j2store/payment_stripe etc.

These files shouldn't be affected by a template update should they?

I'm sorry, I'm not very technical but have tried to be methodical about it, making a note of all the conflicted, modified and new files and copying them over to the local folder as you said.

seanmcel

Should I just be leaving the 'created by user' files out of it? I just had a concern that these would be overwritten if I didn't put them in the local directory.

seanmcel

Don't worry - I asked the hosting company to restore a backup.

It took me pretty much all day to try and update the template moving the files into the local folder and it didn't work. I'd like a refund please on my annual subscription as this update does not look like it will be possible and I will look around for a simpler template that will update in the normal way.

saguaros

Hi seanmcel

Could you tell me the issue here? We provide JAEM - a free component to help user update template (or other JA Products) easier. Many users use this component without issues, you can simply check the update and click update button to update the new version.

With the 'local' folder, I recommend to use this folder as it's better for keeping your customization in template so that it will not be lost when updating new version. It doesn't relate to the update of template here. I also gave so detailed explanation above already.

Regards