I am getting complaints from community users who say that when they go back and edit an already created event, the start date of the event defaults to whichever day they are editing the event. Here is a comment from one of them:

"Whenever I edit anything in an event I’ve already created, the date of the event defaults to whatever today’s date is and I have to keep re-entering the event date every time I edit something."

What do I need to change so the date doesn't change when a user edits an event?

Thanks,

Adam

Hi, Adam.

Ow... that's very strange. first of all you shouldn't have events on your site... as they are disabled: i.imgur.com/TnXytG3.png
Even SU shouldn't see them in frontend when they are disabled.
Also you have version 4.1.2 but events behave like in older version...

Could you try to remove JomSocial and all it extensions, make sure that files ware removed and install it again (no db data will be lost).

I am using JSPT which is why the they are showing up. Each of the profiletypes have their own jomsocial configuration settings. When you say that it's acting like old events, what exactly do you mean? The reason I am asking is because if readybytes needs to update the jspt component, the more information I can give them as to what it's not doing in the latest version would help ensure they don't leave those out of their next update...

Hi, Adam.

In previous versions we had a bug in events so when you ware editing already running event (start date was in past already) then date was re-set to today’s.
I tested your report on my test site and I can't replicate it.
Could you login to my test site and test it also? I'll send you credentials via PM.

Then you should do another test on your site. Disable JSPT, enable JomSocial events and try again if there will be issue with date.

I did try it on your test site and it seemed to work fine there. It does not work on my site (which is very odd). What function/file controls that field?

Thanks,

Adam

Hi, Adam.

I apologize it took so long - I had few days off.
This is controlled by js scripts.
So could you do a test that I mentioned in PM?
Do a copy and remove JSPT...

Michal,

I unhooked the component went to 100% jomsocial and issue is still there. Don't know where to go from here. Also, did you ever find a solution to the events plugin sorting by creation date instead of event start date?

Thanks,

Adam

Hi, Adam.

As for plugin issue - I saw that Albertus provided solution for that issue: www.jomsocial.com/forum/events/30402-js-...-out-of-order#147878 did you tried it?

As for main issue here. Could you provide us access to your test site so we'll be able to test things there?

Michal,

The link you referenced was more a question to help find the issue and not a resolution as my main issue resides in the community plugin (found as well in the module) like we already established on your test site. So far no resolution on that issue or this one... :(

I have been on vacation the past week so sorry for the delayed reply. I will update my test site info so you can test things out on it. I do have some other modifications (other components) that aren't quite ready for live site yet, so don't mess it up to much ;)

Adam

Hi, Adam.

oh, so it's site under development? We need test site to even break it... be able to uninstall things. Can we do it on that test site?

no it's a test site, not live, but I have a few projects I was working on that I backed up so I hope you don't make to big of a mess, but if you need to try things out to fix the problem, go for it. It's not a live site.

Adam

Hi, Adam.

Ok, I'm testing your system. First what brings my attention is that SU can't uninstall or disable Gantry template elements: i.imgur.com/Czzn51u.png

Was this installation a RocketTheme quickstart?

not sure if it was, but did you try to disable gantry through the gantry component?

Hi, Adam.

No, you can't disable it in template.
Try to recall if it was quickstart as this may be important.
I suspect it was as those elements are locked.
Nevertheless I assign developer to this thread.