User tests: Successful: Unsuccessful:
Fix to "$registeredurlparams not found".
This is the same solution as in the similar bug fix 0cb249a
There appear to be no further instances of this problem in the libraries subdirectory.
Glad you found it Nick, and sorry not to have replied initially.
I must admit I'm slightly losing the will to live over reports and
even fixes for Joomla. This one was submitted six months ago and
I've mostly had silly infighting over it.
Is the new framework (social) environment going to be a bit less
antagonistic and a bit more interested looking for solutions rather
than sticking its head in the sand of "it's fine for me"?
That's certainly not meant as an assault on you, but look at the
number of "I don't know what you're talking about" responses to my
original report.
Regards
Mark Stanton
One small step for mankind...
No problem at all, Mark! Thanks for submitting the fix. That's the hard part :)
Hang in there. Things are getting a lot better. We've had a shortage of volunteers in comparison to the workload, and that's been a main reason for the delay. However, we're seeing an influx of new volunteers and we're working on getting more, while also improving the process.
This is fixed in Joomla 3.1 and 2.5. Thanks for contributing, Mark! I hope you'll be able to help us more, as time allows!
Cheers
Nice to know that's finally laid to rest, thanks Nick.
I'm now a little confused between the CMS, Platform, and Framework,
in as much as I think I've identified a bug in com_content and I
don't know where to report it. Can you point me to something that
tells me?
Many thanks
Mark Stanton
One small step for mankind...
You're welcome, Mark! We're glad we could be of help!
CMS has reabsorbed the platform, so now there's only the CMS and the Framework. To report the bug for com_content , use the following process:
http://docs.joomla.org/Filing_bugs_and_issues
It will get submitted to the CMS and we'll fix things directly.
Hope this helps! Thanks for reporting, Mark! :)
If I label an item in JIssues, it doesn't label it in github. Example:
http://issues.joomla.org/tracker/joomla-cms/4229
#4229
Let me know if I should open up a different issue report for it.
This comment was created with the J!Tracker Application at http://issues.joomla.org/.
@nicksavov do you realy want to comment this here? I think this is a issue on jissues.
lol, and I'm 100% positive that last night I posted this comment in http://issues.joomla.org/tracker/jtracker/425
Check the Issue ID. It's the same as this one.
My guess on what happened is that I was trying to multitask and work on issues in the CMS tracker too, while I left the tab open for http://issues.joomla.org/tracker/jtracker/425 . When I submitted at http://issues.joomla.org/tracker/jtracker/425 , it posted it here because I had switched to the Projects CMS tracker in another tab.
Update: Issue report posted at joomla/jissues#486
Thanks for coding this, Mark!
While we’re transitioning to a new integrated tracker, could you report the issue on our current main tracker at JoomlaCode and cross-reference each with a link to the other? Here’s the process for reporting on the other tracker:
http://docs.joomla.org/Filing_bugs_and_issues
Alternatively, let me know if you’d like me to create it for you and I can go ahead and do that.
Thanks in advance and thanks again for coding this, Mark!