Mambo CMS Tracker

This seems to be related to PHP 5.2.x

Please provide more details about how this is related to PHP 5.2.x.

Unable to replicate under PHP 5.2.5. There is nothing in the core bot code that would be sensitive to php versions.

Need to see specific code examples where 3pd bots fail to fire.

I am one of the guys having this kind of problem. I tried to put an exit() inside the perform() function and nothing happens. This is why we think the bot is not triggered. The File is executed (for example the delete one: SMF_user_delete.php), so putting an exit() at the beginning will give a blank page as result, instead putting the exit() inside the perform function nothing
think Orstio is saying that it is related to PHP 5.2.x (mine is 5.2.0) empirically, because everybody having this problem had this verions of php. I don’t know what else could be useful for you in solving the issue, just let me know if I can do something to help.

Sergiu

Hey guys I just found a bug on the system that load the authenticator bots, not sure if is related with this issue, please check it and let me know.

file includes/core.classes.php, method _botRegister, line 1916, from:

if (is_array($selected)) foreach ($selected as $select) $this->_botRegister($botObject, $select);

to:

if (is_array($selected)) foreach ($selected as $select) $this->_botRegister($botObject, $select, $i);

please note that I added $i, if the fix doesn't help you, then I would create a new ticket.

Thanks for your report.

Hi Andres,

I found something similar in core.classes.php but in the line 3821:

function _botRegister (&$botObject, &$selected, $i) {

      $function = array(&$botObject, 'perform');
      if (!is_callable($function)) return;
      if (is_array($selected)) foreach ($selected as $select) $this->_botRegister($botObject, $select);
      $this->_events[$selected][] = array ($function, $i);
      $this->_registered[$i] = true;
  }

I changed the 4th line to:

if (is_array($selected)) foreach ($selected as $select) $this→_botRegister($botObject, $select, $i);

as you mentioned but nothing changed.

Thank you for your support.

Sergiu, it seems that you are not running Mambo 4.6.5, are you?, can you point me to the Mambot that your are using and have the wrong behavior?

as for my fix, I opened a new task for it http://mambo-developer.org/tracker/index.php?do=details&task_id=433 because is probably another issue

It is the 4.6.5, and I have two different installations with the same problem hosted on the same server. Regarding the number of the line, sorry but the first time when I downloaded the php file there were a lot of spaces between lines, this is the reason why the line 1916 was 3821 for me:) However I can confirm that the bots are not triggered anyway. The mambot is either smf_user_change or smf_user_delete. Thanks again Andres.

Sergiu, is it much to ask if you allow me to debug the problem on your server?, I would need a Mambo installation and ftp access, just let me know if that is possible.

Hi Andres, give me just some time to setup a new installation bridged with smf. By the way, is it ok the cpanel mambo installer? If not, I can do a normal install (however only one of the instllation I have was made with the cpanel installer, the over one is a clean new install). Let me know, ang just give me some time to do it. Thank you :)

I've not used the Cpanel installer for a while, so I'm not sure what release they use, if you haved used succesfully it's ok for me..

Thanks a lot for you effort.

Hi Andres, should I send you a private email with the passwords?

Yes please, you can use the Private Messaging system at forum or send it to andphe at gmail.

Thanks

Okay, I'm bridging the cms to smf. Thank you

Hi there,

let's make this thing clear, as we have a mess over here :)

- The original Orstio's report mention userDelete event and the goodLogin - Sergiu reported smf_user_change or smf_user_delete

I've tested at Sergiu's server, and the goodLogin works, the userChange works from the frontend, (the mambot only get fired from the backend when a password change is performed).

So I can confirm that there is a issue with userDelete, are you guys able to delete users in another instances/servers?