Solgema.fullcalendar AJAX throws error - ajax

Overview
I am running a Plone 4.2.4 server, it is a standalone install and doesn't have any add-ons installed other than Solgema.fullcalendar. Everything installed a-ok (I can see nothing in my buildout output regarding errors or missing dependencies and running my instance in foreground mode shows no problems).
Buildout
Inside of my buildout I have: (as they request on this link)
eggs =
[...]
Solgema.fullcalendar
zcml =
[...]
Solgema.fullcalendar
Process
I followed the instructions in the documentation, going to Add New... > Collection
Then on my collection selecting View > Solgema Fullcalendar
I leave the Calendar Properties tab alone and besides changing the view to `Month' everything else remains the same.
Problem
When clicking on a blank date block, I see a little spinner.gif signifying something is loading, but in my Javascript console I see:
Error: uncaught exception: cannot call methods on dialog prior to initialization;
attempted to call method 'destroy'
This happens via the right click menu also, the right click menu loads but throws the above error once I click any of the buttons contained in it.
I can drag events, and resize them without any problems (however I think something is missing as after either dragging or resizing the event, the browser takes me to the page for that event).
Summary
It seems like I'm missing a Javascript file that was not included in Solgema.fullcalendar however I have no idea what script it was and I am unable to decipher this Javascript error (above).
If anyone has any experience with this, ideas or your thoughts would be greatly appreciated.

Related

is "CKEditor for ASP.NET" deprecated?

I'm looking at the download page for ckeditor and I see that the ASP.NET control was last released in 2014. The version string is 3.6.6.2. Does this mean that the control is deprecated? It seems to work properly w/ 4.4.x, but I'm chasing down some weird ckeditor control issues and I wanted to make sure this isn't somehow the cause.
Some of the weird issues I've been chasing
Sometimes when I'm doing a save via form submit, I'll get an exception thrown by the guts of ckeditor: Uncaught IndexSizeError: Failed to execute 'extend' on 'Selection': 1 is larger than the given node's length.
Selecting text in the control prior to save makes it go away
Only happens in Chrome from what I can tell
If I remove the divarea plugin, that makes it go away
I feel like sometimes I'm getting weird errors with it complaining that jquery is missing when I use the asp.net control -- they don't seem to happen under the markup / script based method. I haven't pinned this down yet.
The overall build is the 3.6.6.2 of the asp.net control. The ckeditor build is 4.4.7. There are custom config.js files used in some places and in some places the control is configured by markup in the asp.net control.

Kendo Panelbar Error

I think i've found a problem with kendo panelbar.
In my project i have a kendo panelbar and sometimes i need all items to be disabled.
The problem is that when all items are disabled and you click anywhere inside the panelbar it raises a javascript error. If you click outside and inside again it raises another. I performed some testes and i guess it may be something related to the fact that kendo panelbar try to put focus in the first enabled item whenever you click in a disabled item.
I thought it was something related to the scripts i have in my project, but i found that this error also occurs in the official telerik panelbar example, but you have to open console in developer tools to see the error because the example runs in a frame of the telerik dojo. You can try it. The link is http://dojo.telerik.com/aXoni
I tried google but didn't find anyone with this problem.
I think its strange no one ever found this bug. Am i doing something wrong or is this really a bug in the telerik panelbar and i have to live with it?
Thanks
This definitely seems like a bug so I went ahead and reported it: https://github.com/telerik/kendo-ui-core/issues/307
In the meantime, you can hack around the problem with a mousedown listener during the capture phase: http://dojo.telerik.com/#tjvantoll/OdIj. It's a bit ugly but it'll avoid the error.

Qtp element recognition through diff modules

Ok this may be a vague question but I have an issue recognizing a webelement in one module (tab) but works completely fine in another tab. This is the same webelement. Everything seems to be same. It's the same form on the gui side with same properties and values.
Now this is another weird part, I can add one to the object repository but when I go to the other tab and try the same qtp becomes extremely slow. The + sign for adding it to the repository appears but when I click it, it gives me a message saying this object cannot be added to the repository.
The Web app uses extJS if that matters and this is a high level webelement that has a constant html id. I'm just puzzled as to why it works in one module but not the other.
There are also some subtabs where you can click on this form. Those work fine but when it comes to capturing this element the issue persists.
Any hypothesis as to why this is happening?
Okay it looks like it works when I took off the visible identification and just identifying it by the html id. I still don't get why taking the visible made a diff but it works.

mod-pagespeed and tree menu behaviour

We're having a very peculiar problem with a site that is using mod-pagespeed. Here's the link in question -
http://www.microsemi.com/applications/
If you try to expand one of the sections by clicking on the '+' sign you need to click twice to open.
However if you disable pagespeed using http://www.microsemi.com/applications/?ModPagespeed=off
The link works correctly.
What is the best way to debug this ? Is is possible to selectively disable javascripts from being processed by mod-pagespeed ?
I'd start first of all with looking at the errors that are thrown up on the page in chrome console:
Uncaught ReferenceError: Tips is not defined www.microsemi.com:43
Failed to load resource http://www.microsemi.com/media/system/js/mootools-more.js.pagespeed.ce.BqakF5Rbjl.js
These are presumably related as the errors vanish on the second link without page-speed. I'd assume the second one must be the reason why two clicks is needed - for some reason there is a javascript file missing using mod_pagespeed - also presumably containing jQuery UI.
I should probably add that it says here mod-pagespeed only seems to be of use for badly written sites. Joomla is well written so as long as you have well functioning extensions there should be negligible difference on your site!

console.log not showing in my firebug

In jsfiddle.net, I have this simple code:
console.log('yep');
alert('hello');
I can see the alert window but nothing in my firebug console.
Is there a reason why ?
I'm encountering it as well on my FF15.
In my case, it is caused by the built-in "web console" in "web developer"
Ctrl+Shift+K
https://developer.mozilla.org/en-US/docs/Tools/Web_Console
Beginning with Firefox 4, the old Error Console has been deprecated in favor of the new, improved Web Console. The Web Console is something of a heads-up display for the web, letting you view error messages and other logged information. In addition, there are methods you can call to output information to the console, making it a useful debugging aid, and you can evaluate JavaScript on the fly.
I'm new to using console.log (I used to use alert()s) and was wondering why I couldn't see console.log messages in Firebug too.
After a several minutes of web searching I realised the console mode was set to 'Debug Info'. Clicking the 'All' button made all my messages appear.
The OP didn't make this particular mistake, admittedly. It's a rookie error, but still non-obvious enough (I haven't used Firebug for a while) to bring me here before I managed to figure it out.
This issue has been fixed in Firebug 1.11.0a5. More info is here
I just had the same issue with firefox 29 Beta (and Australis) Just restart the browser :)
EDIT : seems like its it's not true : on the first page load, it display the log, on the others not (need to open the page in a new tab). Apparently it's queryLoader2 jQuery plugin

Resources