Explosion of webservice/xmlrpc/server.php processes

All tests have been buying a single course.

I only see the problem on the server. It's my hosting company so I have direct access to what is running on the server real time.

All appears normal in the browser - there are no problems or error messages displayed.

It seems to me the problems is happening during the time a person is being enrolled.

As I may have said before, I originally tried to use Hikashop for the store, but this explosion of processes happened there and I assumed it was a Hika shopping cart problem. So I went back to trying Virtuemart and discovered it was there too.

Since the other site i have this set up is working, do you think the issue could be that this one is on two domains? Does that factor into anything in the enrolment process after payment?

> It seems to me the problems is happening during the time a person is being enrolled.
If this were the case, it would also happen when you self-enrol.

To be sure this is only Paypal related, you can do the following:
- unenrol user from last course purchased
- go to shop backend, and set order pending and back to confirmed
- check that user is enroled and the process in the server

I followed those directions:

The user was re-enrolled and the processes started running away again.

Ok, so issue is happening on order confirmation, regardless of how confirmation is done.

When order is confirmed, Joomdle just calls the enrol method for the course, which is the same that it does when you use the Enrol button in a free course.
So, I don't know where the problem might be. At this point, the only think that could be do is to debug the code, to try to see what is happening. Please write to antonio at joomdle com if you want me to try to take a look.

Thanks for all your help so far.

Today the other install that I said was working started generating this same error.

This made me to revisit each step of install. On both installations, when I go to "Editing Role Web Service" the following lines apear where one woudl assing the Joomdle roles (btw, I saw someone else report this on your forum 11 days ago but they hadn't replied to your question about where they were seeing it).

Invalid get_string() identifier: 'joomdle:config' or component 'enrol_joomdle'. Perhaps you are missing $string = ''; in /home/smartdri/public_html/academy/enrol/joomdle/lang/en/enrol_joomdle.php?
line 349 of /lib/classes/string_manager_standard.php: call to debugging()
line 6846 of /lib/moodlelib.php: call to core_string_manager_standard->get_string()
line 3037 of /lib/accesslib.php: call to get_string()
line 2882 of /lib/accesslib.php: call to get_capability_string()
line 118 of /admin/roles/classes/capability_table_base.php: call to get_capability_docs_link()
line 138 of /admin/roles/classes/capability_table_with_risks.php: call to core_role_capability_table_base->display()
line 633 of /admin/roles/classes/define_role_table_advanced.php: call to core_role_capability_table_with_risks->display()
line 267 of /admin/roles/define.php: call to core_role_define_role_table_advanced->display()
Invalid get_string() identifier: 'joomdle:manage' or component 'enrol_joomdle'. Perhaps you are missing $string = ''; in /home/smartdri/public_html/academy/enrol/joomdle/lang/en/enrol_joomdle.php?
line 349 of /lib/classes/string_manager_standard.php: call to debugging()
line 6846 of /lib/moodlelib.php: call to core_string_manager_standard->get_string()
line 3037 of /lib/accesslib.php: call to get_string()
line 2882 of /lib/accesslib.php: call to get_capability_string()
line 118 of /admin/roles/classes/capability_table_base.php: call to get_capability_docs_link()
line 138 of /admin/roles/classes/capability_table_with_risks.php: call to core_role_capability_table_base->display()
line 633 of /admin/roles/classes/define_role_table_advanced.php: call to core_role_capability_table_with_risks->display()
line 267 of /admin/roles/define.php: call to core_role_define_role_table_advanced->display()
Invalid get_string() identifier: 'joomdle:unenrol' or component 'enrol_joomdle'. Perhaps you are missing $string = ''; in /home/smartdri/public_html/academy/enrol/joomdle/lang/en/enrol_joomdle.php?
line 349 of /lib/classes/string_manager_standard.php: call to debugging()
line 6846 of /lib/moodlelib.php: call to core_string_manager_standard->get_string()
line 3037 of /lib/accesslib.php: call to get_string()
line 2882 of /lib/accesslib.php: call to get_capability_string()
line 118 of /admin/roles/classes/capability_table_base.php: call to get_capability_docs_link()
line 138 of /admin/roles/classes/capability_table_with_risks.php: call to core_role_capability_table_base->display()
line 633 of /admin/roles/classes/define_role_table_advanced.php: call to core_role_capability_table_with_risks->display()
line 267 of /admin/roles/define.php: call to core_role_define_role_table_advanced->display()

I found the solution to that webservice/xmlrpc/server.php processes explosion.

In revisiting each setting and looking to see if my server had the latest php extensions and other things, I came across the "connection method" in plugins>authentication>joomdle. It was set to "file_get_contents" and I wondered what would happen if I changed it to "curl" - so I changed it.

I did a full test by buying a course through paypal and everything worked perfectly and flawlessly!

I'm not sure why "file_get_contents" stopped working - probably an update installed somewhere on the server or a setting, but I'm happy to be able to move on to finish my project! I think it is really fixed now.

Thanks again for this great product - it's the only one like it and I hope you keep it going for a long time.

As for the "invalid get_string" error message I mentioned just before this post, I checked and it is still there. I've psoted and subscribed to the other post about that ( www.joomdle.com/forum/installation/12055...get-string-in-moodle ) so if you want to keep this thread pure, I should still get a notification from there.

Thanks for reporting back your findings... I don't know why using file_get_contents would cause that issue, but I am glad you found a workaround.