TOPIC: Another Request Failed v 4.0 Beta2

This is a great extension. I am in the process of moving a site to a new server and instead of moving files, I've opted for a clean J 1.5.14 installation with a known clean template.

After installing the v 4.0 Beta 2, I received the "Request Failed" regardless of what I enabled or disabled in the backend. I then completely removed it and used the Beta 1 version and everything works perfectly.

It looks like there are a lot of these errors on the forum and they are somewhat inconsistent as to what is triggering them. My first thought was that it might have been another Ajax application but that proved to be false. All I can tell you for sure is that there is definitely an
Ajax issue on the Beta 2 and instead of receiving the message that the info will be sent to the moderator, the XML CData is displayed in the text box.

Nonetheless, this is an outstanding extension and deserves 5 stars! Thanks mate!

Indeed this is strange, I updated two of three of my localhost test sites with Beta 2 and havn't enountered the issue but obviously something has changed in Beta 2 is causing problems for many.

Out of curiosity (to compare with my own and even do my own tests), what version of PHP are you running and what Browser and Version did you get the error in? We usually only test on Internet Explorer 8, Firefox 3.5 and sometimes Opera 9.6x (Not sure about Daniel, but I never test in IE7, Firefox 3.0, Chrome or Safari although I really should start with Safari)

Thanks for the reply Jonus, the site is running on PHP 5.2.6 and I routinely test on all major browser platforms include IE7/8, FF 3/3.5, Opera and Safari.

I can tell you that I tried every mod that you had listed on the forum (and a few that you didn't) so I obviously did not have a handle on the problem. While I would very much like to help you find it, I'm afraid my work load is not permitting at the moment.

It's curious how the Beta 2 helped some people and in my case, the Beta 1 ends up being the hat trick. Speaking of magic hats, I suspect that your developer Daniel is beginning to get an idea where the problem must be or at least the part of the code that's not quite stable yet.

I will send anything I find to you and keep an eye on new Beta versions as they appear. In the meantime, it works perfectly so I will leave it alone.

Many thanks, Dan

Dan wrote:

Thanks for the reply Jonus, the site is running on PHP 5.2.6 and I routinely test on all major browser platforms include IE7/8, FF 3/3.5, Opera and Safari.

So it's not that... I am running PHP 5.2.9 but I highly doubt it is a PHP bug, here's the changes made against keyword match 'Request' between 5.2.6 > 5.2.9 though just for records sake (It means little to me though )...

- Fixed bug #46760 (SoapClient doRequest fails when proxy is used). (Felipe)
- Fixed bug #45691 (Some per-dir or runtime settings may leak into other requests). (Moriyoshi)
- Fixed bug #45522 (FCGI_GET_VALUES request does not return supplied values).
- Fixed bug #45352 (Segmentation fault because of tick function on second
request). (Dmitry)
- Fixed bug #45312 (Segmentation fault on second request for array functions).
(Dmitry)

I can tell you that I tried every mod that you had listed on the forum (and a few that you didn't) so I obviously did not have a handle on the problem. While I would very much like to help you find it, I'm afraid my work load is not permitting at the moment.

Understandable, if the site needs to be active there's no reason for me to expect you to "try this or this" As such we'll try hard to replicate the issue as soon as we can, keep an eye on this thread incase we ask for some extra info. And FYI, there will be many more modifications to come some things are currently impossible to provide an on/off option for in the current code.

It's curious how the Beta 2 helped some people and in my case, the Beta 1 ends up being the hat trick. Speaking of magic hats, I suspect that your developer Daniel is beginning to get an idea where the problem must be or at least the part of the code that's not quite stable yet.

Agreed it is strange. I'll probably do a full subversion code comparison between Beta 1 and Beta 2 just to see the specific changes - hopefully that'll at least narrow it down to the possible culprit block of code. In regards to the code being unstable, well it's pretty solid I know just enough about PHP to know that Daniel knows what he's doing (and even watching the individual changes am quite impressed with his abilities) but the truth is that JoomlaComment is due for an entire re-write as it's adapted from Joomla 1.x. But of course such a thing is an immense task and is not even planned or on the roadmap at all (for JoomlaComment 5 even). Regardless, I think Daniel has a good grip on the project - any question I have he usually tells me where the code is off his memory (and is right most of the time)


No worries Dan, thanks for your bug report. We'll let you know if there's anything else we need

Hey Dan,
I cannot agreee with you that the "request failed" error message is inconsistent.
It sounds really strange to me that with beta1 everything was working but with beta2 it doesn't. DId you look in the php error_log? Is there some info? Perhaps you can turn all php errors on, icluding notices and see what the output is. Sometimes there are some variables that are not defined and that causes us troubles.

DId you check the folder and file permissions?
In beta2 there are a lot of new language files? Do you use the standard english one or another language? Did you make any changes to the templates after installing beta2?

Hi Daniel,
Then would you say (for the sake of semantics) that the problem is consistent?
Wouldn't it occur on all sites under all circumstances identically?
While I do not have enough time to give you more feedback, I can say that on a clean J 1.5.14 install with the template I'm using (English language) the problem was encountered with Beta 2. Once the Beta 2 was removed and the Beta 1 installed, the problem went away and the extension worked flawlessly.
Everything aside, you have done a remarkable job on this extension and your work is very much appreciated. I will try to get back to this on the live site and see if I can pull up the error logs but for now, my work load doesn't permit
Again, many thanks!
Dan

Hey there Dan,
I can not ensure that joomlacomment will work on all server configurations out there - this is impossible.

What i'm sure about - 2 identical servers will always get the same result.

Next thing - if I don't have the user feedback (your and from other users) I can not ensure that RC one will work for you either.

If you have time; I will be happy to find where the problem is coming from. If not then let us hope that rc1 will work