Calendar.setup: Nothing to setup (no fields found).

[Jay313]

Greetings,

I'm using Joomla 3.5 and SP Page Builder 1.08

All of a sudden I'm getting this error message when I try to save an edit under component SP Page Builder: I'm not having this issue anywhere else on my site. The popup window message I'm receiving when I try and edit a page under SP page Builder is following:

Calendar.setup:
Nothing to setup (no fields found). Please check your code "

Because of this error message, I cannot save my edits. The Save / Save & Close" buttons don't work under this component.

I narrowed down the issue. it's a conflict between my template and Sp page Builder. When I uninstall my current template - SP Page Builder works as it should.

Can anyone shed some light on this?

Thanks,
James

[Olive67]

Hello,
I am having the same problem: "Calendar.setup: Nothing to setup (no fields found). Please check your code" with the component SP Page Builder (in the backend)...
And then I can't access any more to the page I created.
Did you finally get some information about this, and find some solution?
It would be very helpful if you could inform me.
Thanks,
Olivier

[FlapJackSC]

Here's 1 thing that can cause this javascript alert to pop... (high level)

For each call to JHTML::calendar, a chunk of Javascript is created.
When the javascript executes on ready, setup() is called for each use of JHTML::calendar.
That code expects to find a Calendar input on the rendered page.
If, for whatever reason, the Calendar input isn't rendered on the page, the alert pops.

For example, if the code below is a part of a page being rendered:

$cal = JHTML::calendar( ... );
// echo $cal;

The alert pops because the javascript can't find the calendar input (no fields found message).
Un-comment the echo and the alert goes away.

I think.
For those wondering what might be happening when they see this.

[AMurray]

I'm using Joomla 3.5 and SP Page Builder 1.08

Your Joomla version is out of date; advise to update to the current version 3.6.5

A second observation, you're using a very old version of SP Page Builder and would guess there lies the problem you're having. SP Page Builder (according to the JED) is at Version 2.4.1 as at 17th March 2017. I'd update that, and then check if the same problem occurs. If it still happens, but only when using your mentioned template and no other template (e.g. test with Protostar) then you can effectively conclude your template may be conflicting with it. Check if your template has any updates for it.

[AMurray]

I just realised the OP posted this question in May 2016.....but my advice still stands.