User tests: Successful: Unsuccessful:
Second parameter in script
function should be now false
for tabstate
function. This is because this tabs-state.js requires JQuery not full Mootools framework. Setting this to true
not only load Mootools when it is not required but also cause some conflicts if websites that depends on JQuery without noConflict.
Whilst we're finalizing the build of our github based tracker
Now that's what I call positive thinking :)
Hi.
There was some changes in bug reporting for Joomla and im pretty
confused right now with whole process.
I thought I should now report bugs in github joomla-cms or if required
joomla-framework. I would be clad if you could explain it to me. Cause I
do work on Joomla a lot I'm sure I'll need it soon or later.
So the framework is pretty much standalone at the moment from the CMS. The only time you should push to the framework is if you're changing the framework. Only the Dependancy Injection stuff from the framework is included in the CMS (and that isn't actually used by core at the moment). The framework won't start to be used properly until Joomla 4 or Joomla 5
The Joomla CMS requires that you submit the bug report on our tracker at the link I gave above. If you are going to contribute a fix - create the fix on github and then add the link of the pull request to the tracker item. It just means we can check the number of testers on a PR and filter the PR's better than you can natively on github.
Does this help a bit more (sorry it's a right mess)
I think I understand now. So in short I should contribute fix in github if possible and then create ticket in forge.joomla.org project's bug tracker with linking to pull request.
Yes :) Bang on the money! If you don't know how to fix it you can still create a ticket and other people can work on it
Ok so I'll create ticket tomorrow.
Awesome thanks :) Once again sorry for this being such a mess - we are working on it with a tracker that will be integrated with github which should be out soon!
That would be great cause I like speed and interface of github. What I
can't say about forge.joomla.org.
I think we all think that :)
I didn't distribute a read ahead for my #JWC13 #jtracker session. Stop
spreading rumors about my plans ;-)
On Friday, November 8, 2013, George Wilson wrote:
P.S. @elkuku https://github.com/elkuku i was under the impression a
v1.0 was all that far away judging from the number of issues left on github
and i'm also sure i heard rumours of a beta floating around.—
Reply to this email directly or view it on GitHub#2449 (comment)
.
Don't be shy ;D
Yes, well I think we are about to finalize some alpha or even beta in the next couple of.. I don't know... the more hands and eyes we have, the faster we will get something to work with
Thanks @artur-stepien!
Hi,
Thanks for this contribution - it's very much appreciated. Whilst we're finalizing the build of our github based tracker we also need you to please create a support tracker at http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103
If you don't want to do this let me know and I'll do it for you!
Thanks Again :)