To reproduce Issue you mean: Refresh same Page in different Browsers (Firefox, Safari) and different Systems (Mac, Linux) at same Time and then you get Source url can not be empty!?

Source url can not be empty!

This is not a string in the core of joomla

franz, correct, but MacOS and Windows.

brian, perhaps not, but the site worked before 3.7.3, and now does not.

so we need to know where that message comes from in order to try and debug and solve

just checked and it's being called from the template I am using, which is based on JooStrap v2.

<title>0 - Error: 0</title>
<link rel="stylesheet" href="/templates/joostrap_v2/css/system/error.css" type="text/css" />
</head>

@onedego so its a Template-Issue. Please talk to Template-Dev. and close this Issue, thanks.

I wouldn't be so sure about that. The template worked yesterday on 3.7.2. I updated what is supposed to be a minor update to 3.7.3, and now it doesnt work. So the update has broken the template.

You cannot conclude it is a template issue - it might be just an issue that is being displayed by the template in a way we dont recognise. You can test if that is the case by temperarily switching to the protostar template

where can i get the prostar template from? (have always tried to keep things minimalist)

where can i get the prostar template from? (have always tried to keep things minimalist)

If you go to the Extension Manager's Discover page and discover uninstalled extensions it's probably sitting in your filesystem. It's really not advisable to completely uninstall extensions shipped with core, disable them if you desire but don't uninstall them (they end up back on your filesystem anyway when you update Joomla).

thanks mbabker, okay, so the Prostar template does work

just to add, this seems to be the case on the other Joostrap templates I have on the site (3 versions)

Add: Looks like a similar problem. We use Joomspirit templates. From joomla 2.5 until 3.7.2 it worked perfect. Updated yesterday to 3.7.3 The template is not working. Installed other templates from Joomspirit same bad result under 3.7.3. Tried it on an other server same bad result. Installed templates from Joomdev the free ones they works perfect under 3.7.3. We run ESXi on windows server 2012R2. All plugins updated to the latest. Went back to 3.7.2 for now.

thanks for adding on Werkverweg - can you tell me if there's an easy way to get back to 3.7.2 without restoring the site?

Hi, I,am afraid I cannot help you with this one other then say do you have a backup? We run a virtual server so we just go back to the snapshot we always make.

closed as no Core Issue.

Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/16972

@franz-wohlkoenig - How can this be 'no core issue' - you have me with a Joostrap template, and @Werkverweg with a Joomspirit template both of which broke as a result of the 3.7.3 update. You can't say it's not a core issue when it breaks things that work perfectly well before the update. Please re-open the issue.

It is suggested to contact the template developers and get from them a patch, and to help solve the issue in the future, ask them to post here what they had to change to get their templates to work in 3.7.3.
It will therefore be easier to track down the issue as it may come from an error on their side that that have let joomla < 3.7.3 forgive the error, but not anymore 3.7.3.
Knowing what they had to change will let us know if core is responsible or not.

Just to add also, in the core Joomla package and from what I could ascertain the core PHP engine, there is not a "Source url can not be empty" error message. So whatever is giving the error seems to be localized to templates (why so many I can't say, but I've seen it with a few template frameworks now). If there is a core change that can be identified as a culprit, we can re-open and investigate further, but based on the data we have right now there isn't enough to pursue this as a core bug.

@onedego i closed Issue as it looks like an Template-Issue (no Issue using Protostar). This Issue can always be reopen if its a Core Issue to solve a Bug.

Just to add, one of our members, using the RocketTheme Voxel template is experiencing the same issue after the Joomla update to 3.7.3

It may not be the template as RT Voxel works just fine for me. Maybe it is some module in the page?

BTW, blaming a 3rd party template just because there is no error with Protostar is a joke. Lots of modules won't get loaded when switching templates due to module positions being named differently.

Just adding here that I found this on a site and it turned out to be a plugin called "dpcalendar" causing the issue. specifically "dpcalendar upcoming" plugin - once disabled the site then works again with J3.7.3.

Nobody is trying to explicitly blame a template or extension. But right now there is no concrete data to say there is a core bug that we can fix (the error message does not exist in our package and when I scanned the PHP source repo I couldn't find anything like it there). There are 261 commits in the 3.7.2 to 3.7.3 diff, it's not a simple "this is the culprit" thing.

If someone can provide concrete data (stack traces help here) showing where the error is originating from, and we can use that to figure out if something in core is causing the issue, then we can address it. With nothing but a "Source url can not be empty" error string and a "all I did was update to 3.7.3" reproduction instruction, there is simply not enough information to classify this as a core bug.

There was simply not enough information to classify this as a template bug either. :)

And that's why I've tried to be careful with explicitly saying that other than noting every report of this message I've seen has seemingly been related to the template in use. The DPCalendar comment is new info to me.

I must admit I was very surprised that this issue was closed without real investigation as a "must be a template issue".

Anyway I hope the extra info I provided about it being dpcalendar plugin in my case helps you...

@laoneo Maybe something for you since DPCalendar got mentioned 😄

I just disabled the DPCalendar Upcoming module in my site and it is working again...

Yes it's a bug in DPCalendar which got fixed in version 6.0.9 which was released today. Please upgrade to the latest version and then the error should be gone.

Confirmed - updated and working fine. Thanks to all and apologies.