DTH Development

Just completed another upgrade in preparation to moving to J1.7 and got the following error on every event.

Warning: Invalid argument supplied for foreach() in /home/mtbskill/public_html/administrator/components/com_dtregister/models/event.php on line 669

Warning: Invalid argument supplied for foreach() in /home/mtbskill/public_html/administrator/components/com_dtregister/models/event.php on line 669

Warning: Invalid argument supplied for foreach() in /home/mtbskill/public_html/administrator/components/com_dtregister/models/user.php on line 2025

I've saved the config again, but still the same error

Addition to this... and the event won't go past the final NEXT screen.

We addressed this through a ticket, but as the issue is double-posted here, we'll answer here too. This wasn't actually a DT Register problem. It was due to template overrides that had been setup.

In 2.7.14, all session handling was revamped so that required updates to many files. This site was pulling in old DT Reg files that were missing the necessary session-related changes. We applied the needed changes to those files and all is well now.

For anyone that does these type of overrides to make your own customizations to the look of anything in DT Reg... If you ever update and see odd issues like this user did, the first thing you should check is the new package to see if the timestamp on any of the template files that you have modified versions of have been updated. If so, you'll need to get the updated version in place. You can't assume those files will never be modified Thanks!

Now that I've had time to digest this, it's occured to me that somethings not quite right with what you've said.

The whole concept behind a truc MVC model is that I can make changes to the view without effecting the core, hence a non core hack.

That's the way the Joomla templating system is supposed to (and does) work.

If we were to have to change our view layouts with every update, then what's the point of the HTML folder within the template?

Might I suggest that you really do need to rethink this strategy.

At worst you probably need to simply use an include file at the top of each view file, and just update this.

I'm a full time Joomla developer and I depend on override files in order to do my job. I use JomSocial extensively and certainly could achieve the end result if I didn't have access to the overrides. I've upgraded many times with JomSocial and never encountered this.

Yet I'm sure this situation with your product has happened before. I'm very angry at myself for not remembering this.

Guys, we need a solid robust system that's not going to BREAK with updates.

So... this IS a DTRegister problem, because you are not following the correct MVC protocol... OR you need to make sure this is WELL DOCUMENTED in your upgrade instructions.

Again, you KNOW I'm a very loyal and longtime user. I need you to continue to build an awesome product. But this practice needs to be changed.

Look forward to your response.

Further to this.

I've now upgraded to the even latest version.

To my surprise it would now appear that HTML overrides are NOT being applied.

I've copied the new versions of the files into the HTML override folder and made changes... nothing happens. Yet if I apply the same changes to the core files they apply.

Please, tell me this is a simple oversight. Please tell me this is NOT by design.

Hey everyone, I just encountered this same error after upgrading to version 2.7.14 and reading through these threads I have to agree with normdouglas and you know I am a veteran user of this great component.

I'm using Joomla 1.5.26 and never needed to upgrade any template.

So, what is the fix? Anyone?

You can't assume that the tmpl files will never be updated. There were LOTS of changes from 2.7.13 - 2.7.15 that affected pretty much everything... as queries and session handling were modified across the board... required that lots of files get modifications. Most were minor, but it was one of those times where more changes than the normal were made.

If a template file has anything that needs updated... then we'll update it. The solution would be to probably just note when tmpl files get modified in an update. As a precaution, never just assume. If you've done any overrides, you should be verifying that your changes are not affecting anything else.

By the way, just to clarify, this discussion has nothing to do with your Joomla template. Norm is talking about what Joomla calls template overrides... but it's not the actual site template. It is overriding actual DT Register files with your own versions so you can modify layout and such and NOT lose those changes when you upgrade the component. The "template" files within DT Register are not usually modified so this is safe, but as seen recently, sometimes it may be needed.

So, are you suggesting that I reinstall the component alone as the modules and plugins should be okay?

This is what I am getting after someone registers. As you can see, the Event_Name is not displaying either.

You said here that you had updated to 2.7.14. Is that correct? The current is 2.7.15b so you need to make that update.

By default, when an update is released, you do not need to update modules and plugins. We always give full details with every update and if anything is done to any module or plugin, it is stated in the release notes.

FYI, I installed the latest version of 2.7.15 and that seemed to fix the warning error message.

Thanks again.