Topic-icon Incompatibility issue?

Active Subscriptions:

None
14 years 6 months ago #16077 by guygoo
There's a possible conflict between JFBConnect 4.0.3 and Jomsosial 2.4.1 Events

Symptom:
Two warning pop-up appears in browsers (tested with Firefox and explorer). Turning off ical in JS events plug-in did not help.
However, turning OFF the whole events extension did!
So, this leads to the question, how to have both JFBConnect 4.0.3 and Jomsosial 2.4.1 Events activated at the same time?

Thanks in advance for a positive solution.

Cheers!

WARNING 1
Calendar.setup:
Nothing to setup (no fields found). Please check your code
WARNING 2
Calendar.setup: Nothing to setup (no fields found). Please check your code
Prevent this page from creating additional dialogues
The topic has been locked.
Support Specialist
14 years 6 months ago #16080 by alzander
Replied by alzander on topic Incompatibility issue?
Guy,
We've heard of this issue 2 other times over the last 6 months or so.. so it's very rare. In each case, we haven't been able to get nearly as much information as you've just provided. Thank you!

Without more information, it will be hard to diagnose, but you seem ready and willing to help. Mainly, we need to be able to recreate this problem on one of our development sites if possible. Can you let us know the information below? Just so you know, I'm not terribly familiar with the JomSocial Events stuff, so some of this may sound pretty rudimentary:
1) When you say "However, turning OFF the whole events extension did!", you mean the "Enable Events" setting in the Configuration -> Events area of JomSocial right?
2) When do you get this pop-up error? Is it only on specific pages, or any JomSocial page you visit? Can you give the URL (domain not necessary, mainly the /index.php? portion, if possible)
3) Any other configuration options or navigations paths that make this error popup would be great to have!

In the past, we've had to say "go talk to JomSocial about it".. which is true, since the error is in their extension.. it's very possible we wont' be able to fix the problem, but if we can narrow it down with your info, that would really help to make progress!

Thanks,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 6 months ago #16111 by guygoo
Replied by guygoo on topic Incompatibility issue?
Hi,

alzander wrote: 1) When you say "However, turning OFF the whole events extension did!", you mean the "Enable Events" setting in the Configuration -> Events area of JomSocial right?

Yes

2) When do you get this pop-up error? Is it only on specific pages, or any JomSocial page you visit? Can you give the URL (domain not necessary, mainly the /index.php? portion, if possible)

Here's a couple of examples: Upon entering the site or when clicking on Facebook connect.

3) Any other configuration options or navigations paths that make this error popup would be great to have!


Yep :) I'm getting closer... I'm using a plug-in from JoomlArt T3 version 2. I have turned all file compression off from within the plug-in and tested. FBconnect and JS events have worked a day or so with no warnings popping up.
It's possible compression/minifying might be the problem and not the actual JA extension? I'm conducting more testing in a lab environment and I'll let you know the results...

Cheers, Guy
The topic has been locked.
Support Specialist
14 years 6 months ago #16124 by alzander
Replied by alzander on topic Incompatibility issue?
Guy,
That's definitely a good deduction on your part. Compressing the files really should be the problem (that usually just strips whitespace, but should functionally change anything). However, minification can do some crazy things and is likely the culprit. That will combine multiple Javascript files into one big file, which generally isn't bad, but dependencies, ordering problems, or other issues can easily arise when everything is mushed together.

I'd try re-enabling compression and see how that goes. Minification may just have to remain disabled though.

Definitely keep us posted on what you find,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 6 months ago #16140 by guygoo
Replied by guygoo on topic Incompatibility issue?
Joomla 1.7.3
JS 2.4.1
JA T3 Framework Version 2 plug-in ( wiki.joomlart.com/wiki/JA_T3_Framework_2...olor_Contrast_Themes )
JFBConnect 4.0.3

Extensive trial and error testing has given the following solution using the above:

JA T3 V2 plug-in settings:
1. The settings within JA T3 plug-in are in this scenario the solution to solving the problem and point 1a. the most important .
a. Enable Development Mode - if you set this setting to Yes, it will completely disable all cache, so that you can always see instantly your customizations on page refresh. Setting this setting to No is recommended for production websites with huge traffic that need cache.
This is now set to YES

b. Both CSS and JS are set to Join & Minify & Compress

c. Optimize folder - t3-assets

Joomla 1.7.3 settings:
d. Gzip Page Compression Yes

e. Cache - Still testing this but set to ON - Progressive caching. All is well so far :)

I'm using a third party extension called Cometchat 4.0 and because this does not support https at present, I'm using htaccess to redirect to http

I hope this helps for similar setups or maybe gives a clue to a step in the right direction.

Cheers, Guy
The topic has been locked.
Support Specialist
14 years 6 months ago #16145 by alzander
Replied by alzander on topic Incompatibility issue?
Guy,
Thanks so much for your feedback. We'll definitely keep this post in mind if others ask, and may add it to our JomSocial common support questions area, at least as a starting point for the few users that seem to run into this. We really appreciate you're help since we haven't been able to recreate this, which makes it terribly difficult to make any progress toward a resolution.

Thanks again,
Alex
The topic has been locked.
Active Subscriptions:

None
14 years 6 months ago #16323 by jeromeuy
Replied by jeromeuy on topic Incompatibility issue?
That's great. :)
The topic has been locked.