Joomdle does not enrol user after Virtuemart purchase

As the title suggests, I am having problems with the enrolment after a purchase. I am working on a site using:

• Joomla 2.5.27
• VM 2.6.12
• Joomdle 0.95
• Moodle 2.6.6

I have followed through the instructions on the site, but cannot find anywhere that I may have gone wrong when setting this integration up.

I have checked and confirmed that these are correct:

• Correct category
• Manual enrol method enabled in course
• joomdlevm2 plugin enabled

In Virtuemart, the payment is accepted and the order status gets changed to confirmed, but nothing further happens with regards to the enrolment process.
I also noticed recently, that although Joomdle had pulled all of the required courses into the Shop listing within the component, there was 1 course which it has not placed into the Virtuemart store whilst all of the others have been added.

Using "System Check" shows that everything is working correctly between Joomla and Moodle.

Has anybody had a similar issue? Any suggestions / help would be greatly appreciated, thanks!

It seems you checked almost everything, Just make sure "buy courses for children" is disabled.

It seems that this was set incorrectly. This was not originally the case, but unfortunately there are several people with admin access, so I don't know who did it! Thanks so much for assisting with that.

I also mentioned that there is just 1 course which does not get created in the Virtuemart products section.
The course has Joomdle set as an enrolment method and shows in the "shop" area of the Joomdle component in Joomla but if it is toggled to "sell on shop", it does nothing. It is not added into the VM store products at all and although it displays on the frontend of Joomla with a "Buy Course" button, when the button is clicked it brings up a "404" error.
Can you think of anything that could be causing this?

Great to know that you got it working.

As for your other problem: most times I've seen this, it was caused by a duplicate alias. Check that you don't have any products in shop with the same title as the course.

Hi Antonio,

I have checked thoroughly and can confirm the following course counts:

• DB: virtuemart_products = 11 (10 courses + 1 bundle)
• Virtuemart: products = 11 (10 courses + 1 bundle)
• Joomdle: shop = 12 (11 courses + 1 bundle)

There are no duplicates in the course alias/titles in either moodle, Joomdle or Virtuemart.

So, there is one product that appears as published in Joomdle shop, but is not in VM table?

You can try deleting the product in Joomdle->shop, and creating it again. Does it show any error when doing so?

Yes, that's correct. It's in Moodle & Joomdle but not VM.

It is not possible to delete the item from the Joomdle shop tab and initially there is no error on screen.

If I turn on Error reporting to "Development" level, I get a lot of errors listed just by going to the "shop" tab but this error seems to be directly related to rhe "shop" function in Joomdle on that tab:

Strict Standards: Non-static method JoomdleHelperShop::is_course_on_sell_on_vm2() should not be called statically, assuming $this from incompatible context in ..../administrator/components/com_joomdle/helpers/shop.php on line 1089 Strict Standards: Only variables should be assigned by reference in ..../administrator/components/com_joomdle/helpers/shop.php on line 1098

(On "Maximum" there is no error displayed but still cannot delete).

Hi again Antonio,

An update on this situation, in case it helps anyone else out.

I could not remove the course from Joomdle and it obviously did not display in VM anyway, so I went to the course directly in Moodle and changed the staus of it to "Hidden" which obviously stopped it from displaying in Joomdle's "Shop" tab. I cleared the cache in Joomla (Just in case it was a contributing factor) and then went back into Moodle and set the course to "Show" again.
Once I had done this, it displayed again in Joomdle's "Shop" tab and was also published into the VM products list.

Thanks for your advice and I hope that this might be useful to other users in the event that they experience the same issues.

Thanks for your sharing your solution.

I don't quite understand what happened, but the good thing is that it's working