Resolved Pages for Module Import

Hello Ian,
Thank you for confirming that the patch worked. As of now we don't have an ETA for the next release but i can assure you that the fix will be included in the upcoming version.

Hi Tharuna,

That looks like it did the trick, thanks. When is the next complete version (with this fix in) likely to be released?

Hello Ian,
Thank you for sending the debug log and import file. It helped me to find an issue and its fixed with the attached patch file. Can you load the patch file and give your import a try?


patch_modules_2018_05_31.zip

I've emailed you a log and an example import file. Let me know if you don't receive them.

Thanks

I don't think I had logging enabled on the last run; I'll try it again shortly and share the log if it happens again.

Hello,

I'm not using menuid at all and I imported my modules yesterday and they were all associated with no pages.

Can you post your import file and import debug log to check? Check How to get debug information? document to get the debug log.

Can I force them by using a menuid of '*' for example?

You should be using 0 instead of * to assign them to all pages.

Hi Tharuna,

Thanks for clarifying.

That's odd. I'm not using menuid at all and I imported my modules yesterday and they were all associated with no pages. Can I force them by using a menuid of '*' for example?

Hello,
When you are importing new modules and no menu is set then CSVI will set the default to appear on all pages on import. If you want to set the menu to specific pages then you can use the field menuid. Multiple menu ids seperated by |.

For the modules which needs to be updated with new menuids, you need to set processmenu to Yes in your template settings on Options tab to process them.