Hi

I just noticed that there is an pop up saying "Please select your location" when I keep window size big enough when I try to register via quick registration.
However the pop up disappears when I narrow window to validate responsive UI.
Other mandatory fields ( password etc ) have red outline when I narrow window, so users would still understand they are mandatory, Also if I leave password field blank for instance, register button doesn't allow to execute as opposed to when I leave only address blank,
it redirects to full registration with error message "There was some error in the registration form. Please proceed with full registration."at the top of the page.

This is very confusing from user's perspective.

Hi Shimizu,

Sorry for late reply to this,

Can I have permission to help you update to latest version of Easysocial?

because I tested in my locally it work fine in 1.3.28.

Hi

Thank you for your response. I thought I use the latest easysocial as it is a message "Awesome! You are running on the latest version of EasySocial.Installed version: 1.3.23"
I am not too sure how to grand permission to you to install the latest version of easy social. please use admin account I have attached with my original post.

Thanks

If you've given at least Joomla's Super Admin credentials, that should do it.

I have provided a super admin credential with my first post...
Anyway, I just added it again, please try.

hi Hi Shimizu,

I'm really sorry that delayed of this reply,

What my mean is actually I afraid you have do some customization work in your Easysocial, if I didn't ask for the permission and I update to latest version directly, it will override all of your customization work to original code.

After updated latest version of Easysocial in your site, it seems like that was some cached issues because I tested around, the script still can't load properly if the address field is empty value. After investigate long time ago, it seems like this plugin "System - Page Cache" causing this issues, I have temporary disable it, it will show out the alert message, take a look of my video link -> http://screen.stackideas.com/2015-07-06_1052.swf

Hope this help.

I didn't realize that upgrading version will delete all the custom work, it seems that you have done it already. my developer is in shock as he didn't have back up of his work at his local. He is demanding payment again if I want him to do exactly the same that he already has done.

Please roll it back to the original and ensure that custom works remains as it was.

Many thanks

Hi Shimizu,

I'm really sorry about that

Hmm that was no other way to roll back to your previously custom work, perhaps you can try using your Akeeba backup revert back to your previous version and see how it goes.

Or see if your host maintains an incremental backup. Those usually cost to be used, though.

I am in a bit of shock now.. it sounds like it is going to cost me a lot..
I will try backup system...

Can you please clarify below for the time being?

1. All the customization were deleted or simply stopped working as it was not meant to work for the different version?
2 How do others upgrade to new version if they have also customized scripts?

Hello Hi Shimizu,

Yes, you also can try David suggestion and check from your webhosting provider and try consult with Akeeba backup developer, If I'm not wrong this extension will do the version backup, If i recall correctly, your Easysocial previously version is 1.3.23.

1. All the customization were deleted or simply stopped working as it was not meant to work for the different version?
>> May i know which file you customized? If they customize on Easysocial core file, all will get overwritten when doing the update.

2 How do others upgrade to new version if they have also customized scripts?
>> Based on what I knew is they will backup their customization file before update.


By the way, thanks for sharing David.

No problem; glad to put what I learned at a hosting company to good use. :P

Thank you for your response, Fortunately my hosting company has weekly backup.
The latest backup was taken on 6/7/2015 at 01:38.
They are having an issue finding the version number....

Could you please let me know what the file path is to locate the version number?
I need to ensure that the latest backup is with 1.3.23.

Thanks

/administrator/components/com_easysocial/easysocial.xml

Hi David,

Thanks for sharing.

Hello Hi Shimizu,

Please let us know how it goes.

I am sorry for the inconvenience caused.

Much appreciate David,
However production site still runs with 1.3.23,
Arlex run upgrade to dev node only.

@EasySocual Suppot

Please let me know the relevant path of this particular node?
Cpanel of nyt hosting is currently down, so I am not able to check it myself,

I'm a bit lost. What do you mean by node? If you're trying to verify if your backup has the proper version you would use that path to find out. All extensions hold their version number in the XML file.

Wherever your development path is, that directory is still relevant. It's all relative.

Hello Shimizu,

I am really sorry but I am having a hard time understanding your issues here. As David pointed out earlier, the path to determine the version of EasySocial is at /administrator/components/com_easysocial/easysocial.xml under the "version" node.

Hi Shimizu wrote:

How do others upgrade to new version if they have also customized scripts?

I personally use a template over ride to keep my 1 modification to an ES module. Upgrades do not break it. Another tactic I do is use a test site to test a upgrade. You can either use it for upgrade tests or simply as a method of containing older scripts/modifications. This alone isn't as good as a backup, but does use a lot less space and is easy to manage. I backup my entire site perhaps every 3 months or so. When I feel I no longer need my test site, I delete the database tables/files and re-copy everything. Then I have a fresh test site for 3 more months or so. Staging like this allows me to go back and get old code as needed. Usually I keep both ES installs up to date for the Stackideas team.

Thanks for the info Josh.

Frequency of backups will be determined by how often new content is created and how mission-critical that data is. I have one colleague who swears by having an incremental daily, full weekly, and full monthly backup. Stored in no less than 3 locations: on-server, locally, and in a remote location (cloud, perhaps). And full backups tested. As read on a security blog, "an untested backup is likely as good as no backup at all".

...but given how tiny my sites currently are, I tend to backup on average 4 times a year. *laughs*

I do, however, tend to use a naming convention on individual backup files " filename.ext-bak" on things I'm testing or don't want to be overridden by an update. Multiple -bak files may get dates on them, but that's rare.

Thanks for sharing David.

Sorry to keep coming back, One last question!

I still need to upgrade ES to 1.3.28. in order to make address mandatory at some point.
There is few quires in order to plan update cos I want to be more careful next time

1. As the latest version is 1.3.23, I guess you haven't published 1.3.28 officially.. ?
2. 1.4 is upcoming according to your roadmap, I would rather upgrade it to 1.4 straight away when it becomes available rather than 1.3.28 and them 1.4. Is the address manadatory fix included in 1.4? If not, please advise what is the best process to implement the fix?

Many thanks

H

Hi Shimizu wrote:

1. As the latest version is 1.3.23, I guess you haven't published 1.3.28 officially.. ?

I've been using 1.3.28 for over a month now. You can see the most modern version in your dashboard of Stackideas.

From another thread, 1.4 is predicted roughly to release months, not weeks from now.

Hi guys,

Thanks for your concern and understanding on this. We're currently swamp with the development and we're trying our best to meet the datelines. Please bear with us for a moment or two. We'll definitely release EasySocial 1.4 and it will be absolutely amazing.

Have a nice day.