TOPIC: 2.7 issues

Now, since the two months "waiting for product" show is over, I was expecting the most perfect component ever. Here are first issues:

1. I couldn't even create one single event in the backend, here is the message I get in the frontend calendar view after I did that: "Fatal error: Call to a member function load() on a non-object in ...../joomla/libraries/joomla/user/user.php on line 597". I am using JomSocial 2.0 but I don't think the issue is related with this.
Interesting is the fact that the event I created is not shown in the backend nether.
Also the problem is still there even after I uninstalled and installed your component.

2. Also, after I enabled DTRegister EventLink plugin, most all my pages (not related with DTRegister component!) dissapeared and I had to spend one hour figuring out what's going on. I guess this is also part of those "2 months of waiting for the coolest, bugs-free version of the new version" process? Anyway, any idea what's going on?

3. I couldn't figure it out any Template entry, so I can enable/disable different fields based on the template I use. You answered one of my questions by saying I can disable the fields I want to hide for adding a simple event and in the same time being able to define complex events from the front end? How?

4. No mini-calendar module? Am I picky to ask for this? Wasn't this one one of the most used module from JEvents?

5. The calendar doesn't fill all the area in the page? Doesn't it have a fixed width? Am I picky again to ask for this?

6. Locations is shared by all users? Since the users can add events from Frontend, woudn't make sense each user to have it's own locations and to be able to manage them from Frontend?

These are my questions without even being able to get an event created. Please try to answer them so I can move forward and try to really use your product.

See comments below...

1. I couldn't even create one single event in the backend, here is the message I get in the frontend calendar view after I did that: "Fatal error: Call to a member function load() on a non-object in ...../joomla/libraries/joomla/user/user.php on line 597".

As many are already using 2.7, this is not a global issue affecting everyone. We can check this directly on your site through a ticket. As we obviously have many tickets and posts at the moment, we're going through as quickly as possible.

2. Also, after I enabled DTRegister EventLink plugin, most all my pages (not related with DTRegister component!) dissapeared and I had to spend one hour figuring out what's going on.

Did you update to the latest version of the plugin? Make sure you are using the plugin from the latest download package.

3. I couldn't figure it out any Template entry, so I can enable/disable different fields based on the template I use.?

Fields used are set per event... on the Fields tab in each event setup... frontend or backend. Your site template has no connection to what fields are used within DT Register. Setup the fields you want for the event. Then when you create another similar event, just COPY the existing event so it will use the same field options.

4. No mini-calendar module? Am I picky to ask for this? Wasn't this one one of the most used module from JEvents?

The mini-calendar module will be coming soon... just didn't make the final cut. Had to get things out and moving ahead. As already discussed in the forum as well as the regular free webinar sessions we've been doing, the module is soon-coming.

5. The calendar doesn't fill all the area in the page? Doesn't it have a fixed width?

The calendar should fill the whole available area. If it doesn't, it's probably related to your template somehow. We could check through a ticket.

6. Locations is shared by all users? Since the users can add events from Frontend, woudn't make sense each user to have it's own locations and to be able to manage them from Frontend?

Locations ARE manageable on the frontend to the users you give permission to. But yes, all locations are shared at this time. Yes, it's true... DT Register is not perfect in every way for every person. If you want to suggest locations to be tied to individual users, that would be a feature request. That goes further than just complaining when it's not there. It's very clear that 2.7 moves much further down the road with frontend access and such. As that is a completely new side of DT Register, it's understandable to put it out there to the level it is... get feedback... then continue to develop based on feedback.

Thanks. We're more than happy to help and working hard to do so. My request is that you just keep your cool. Posts that get ugly will not be kept on the forum as that isn't necessary. We're here to help... not argue with you. Thanks

Also, you had mentioned in another post references to private events not working correctly. Those are not bugs... those are misunderstandings of functionality. Private events are viewable by everyone. The restriction is on who can REGISTER for those events. Only logged in users can register.

The only way to restrict who can VIEW an event is to set the event within a category that is restricted to public, registered or special level access. Just wanted to point this out and make sure you were aware.

2.7c doesn't fix the problem. I can't access the component while I am registered so I can't even see or manage the events from the front end. There is a ticket open since yesterday morning, please answer it asap. The error again is: "Fatal error: Call to a member function load() on a non-object in ............../joomla/libraries/joomla/user/user.php on line 597"

Private is private. It means that the user doesn't want that event to be posted. This is how JEvents and other components work. Redefining English words and claiming it's a missunderstanding of what the feature should do is not good. But we'll go there after at least I can pass through the main issue.

Please next time don't remove my posts. There were other issues I reported in the post you deleted and that post was about 2.7b.

Just in case you haven't seen, 2.7.0e is now available and has addressed a whole list of known issues, including the ones you have mentioned. The announcements forum thread gives more details. Thanks.