Moodle course as product with options

Hello,

I have a problem & need some help.

I have joomdle successfully set up. I can sell & buy courses using my j2store at my website.
My problem is, that if I add some options to the product in the store and order that course I get an XMLRPC Error.

Is there something I can do?

Thank you!

You can enable debugging in Moodle to get more info about the problem.

XML-RPC Error (23604497): Datensatz kann nicht in der Datenbanktabelle course_categories gefunden werden | DEBUG INFO: SELECT id,parent FROM {course_categories} WHERE id IS NULL [array ( )] | ERRORCODE: invalidrecord

XML-RPC Error (23604497): dataset could not be found in course_categories | DEBUG INFO: SELECT id,parent FROM {course_categories} WHERE id IS NULL [array ( )] | ERRORCODE: invalidrecord

That's the Error-Code with debugging enabled. But I still don't know what to do...

Thanks for the info.

Can you tell where/how do you add the options?

Thanks for your support!

I create a course in moodle -> publish it in the joomdle component -> change the type of the shop article from "simple" to "configurable" -> add the options via j2store (I import them from another product)

Find a screenshot of the options in j2store attached

Thanks for the info.

I tested locally and saw that when you add options to a product, J2store changes its sku, removing the Moodle course ID (that we save in sku).
So, it is normal that problems appear.

A solution for this is difficult... if J2store changes sku by itself there is not much we can do
Can you check if this happens to you too?

Thank you very much for this information.

Do you see any reason not to just change back the SKU to the moodle course id?
J2Store changes it, if you change product type to configurable, but it's free to be changed again afterwards...

I tried it just once and it worked fine, so I think this solution works for me

Thanks for the info, we'll leave it as it is for now then.

If you want, you can contact J2Store support and inform them about this, to see if it is a bug in J2Store, or they do it for some reason.