Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script conflict with template Beez3 (BBCode editor will not loading) #2185

Closed
rich20 opened this issue Dec 16, 2013 · 27 comments
Closed

Script conflict with template Beez3 (BBCode editor will not loading) #2185

rich20 opened this issue Dec 16, 2013 · 27 comments

Comments

@rich20
Copy link
Member

rich20 commented Dec 16, 2013

http://www.kunena.org/forum/k-3-0-general-questions/127727-loading-bbcode-editor?start=30#151532
I can confirm this error

TypeError: a is null
../media/system/js/mootools-core.js Line 99

@810
Copy link
Member

810 commented Dec 16, 2013

Issue is templates\beez3\javascript\hide.js line 394:

window.addEvent('domready', function () {
new mobileMenu();
});

@mahagr
Copy link
Member

mahagr commented Dec 17, 2013

So does this bug prevent Kunena from loading the BBCode editor or is it something else? Looks like this is Joomla bug.

@xillibit
Copy link
Member

Issue is templates\beez3\javascript\hide.js line 394:

window.addEvent('domready', function () {
new mobileMenu();
});

What is the issue in javascript console ? How did-you found that this part of code is causing the issue ?

@810
Copy link
Member

810 commented Dec 17, 2013

first what i did was rename the javascript dir. then the bbcode worked, so i know it was in the template/javascript dir. Then i renamed the hide.js , there was the issue. then i removed 1 function a time.

@xillibit
Copy link
Member

Just tested under J3.2.1RC with 3.0.4 and i don't see the issue

@sozzled
Copy link

sozzled commented Dec 17, 2013

So, maybe Matias is right and this was a bug in J! 3.2.0?

@810
Copy link
Member

810 commented Dec 17, 2013

Its a conflict with mootools and jquery.

After this pr it worked:
joomla/joomla-cms#2002

@rich20
Copy link
Member Author

rich20 commented Dec 18, 2013

Confirmed, it works

@mahagr
Copy link
Member

mahagr commented Dec 18, 2013

A bug in Joomla, let's hope that Joomla 3.2.1 fixes this.

@mahagr mahagr closed this as completed Dec 18, 2013
@rich20
Copy link
Member Author

rich20 commented Dec 18, 2013

Unfortunately it is not fixed in J 3.2.1

@mahagr mahagr reopened this Dec 18, 2013
@xillibit
Copy link
Member

I have reproduced and located the source of the issue, i'am going a make a fix in Joomla!

See : joomla/joomla-cms#2709

@810
Copy link
Member

810 commented Mar 2, 2014

I think we can close this issue. its a joomla bug, and still waiting for the merge, i think it will be j3.3

@mahagr
Copy link
Member

mahagr commented Mar 3, 2014

We will keep this open until Joomla fixes it. Just works as a reminder to make sure it gets into J3.3

@810
Copy link
Member

810 commented Mar 8, 2014

Can be closed, its in joomla 3.3

@xillibit
Copy link
Member

xillibit commented Mar 8, 2014

Where do-you see that it's in 3.3 ?

It was targeted against the wrong branch: joomla/joomla-cms#3258

@rich20
Copy link
Member Author

rich20 commented Mar 8, 2014

close or not?

@xillibit
Copy link
Member

xillibit commented Mar 8, 2014

It's not merged in Joomla! for now

@mahagr mahagr modified the milestones: 3.0.6, 3.0.5 Mar 9, 2014
@coder4life
Copy link
Contributor

@xillibit @810 @rich20 was this fixed correctly?

@rich20
Copy link
Member Author

rich20 commented May 4, 2014

Apparently, they do not want resolve the error. Tested with Joomla 3.3.0 and Joomla 3.3.1 DEV

@810
Copy link
Member

810 commented May 4, 2014

Its fixed, can be closed

@coder4life
Copy link
Contributor

Two conflicting sources of information. @rich20 and @810 can you guys work together to see if this is fixed or not.

@xillibit
Copy link
Member

xillibit commented May 4, 2014

I have just tested it under J!3.3 and i'am not to see this issue, so @rich20 i think it can be closed

@810
Copy link
Member

810 commented May 31, 2014

yes, I tried also again. I see no issue.

@rich20
Copy link
Member Author

rich20 commented Jun 1, 2014

Can't confirm it. The error still exists. Tested with J!3.3

@xillibit
Copy link
Member

xillibit commented Jun 1, 2014

I'am not able to reproduce the issue un J!3.3, do-you have a link to see the issue ?

@810
Copy link
Member

810 commented Jun 3, 2014

Is finally in the core. Can be closed now

@xillibit
Copy link
Member

xillibit commented Jun 3, 2014

@rich20 yes it's in joomla! core so i think it will be avaible with J3.3.1 : joomla/joomla-cms#3703, can-you close it ?

@rich20 rich20 closed this as completed Jun 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants