Conversation
supportWhen selecting a preset from the Load Preset dropdown the page refreshes but does not load the template and the drop down is empty again – displaying the “Choose a preset to load”. It’s not possible to load a template.
Hello @scarey149 Can you please share if it is showing any error or screenshot. So we can solve the issue you arefacing. Regards
Not sure if this helps, but I checked the Network payload and the request being sent is action: umef_export_csv
Hello @scarey149 Thanks for sharing the Network payload, that helped us track this down. The <code class=””>action: umef_export_csv you saw was from a background user-count request, not a CSV export. The preset dropdown is inside the export form, so that hidden field showed up in the payload. The real issue was preset names being sanitized differently on save vs. load (e.g. <code class=””>My Export became <code class=””>my-export), so the preset could not be found after the page refreshed. This is fixed in 1.0.5 (will be released by tomorrow). After updating, hard-refresh the export page (Ctrl+F5 / Cmd+Shift+R) and try loading a preset again. If it still fails, send us the preset name and we will take another look.
Hello @scarey149 Have you tried the latest version? Regards
Tested and working perfectly! Thank you for your speedy fix!!
Hello @scarey149 Great to hear that issues is resolved. Thanks for the revised rating 🙂
Hello @scarey149 Can you please share if it is showing any error or screenshot. So we can solve the issue you arefacing. Regards
Not sure if this helps, but I checked the Network payload and the request being sent is action: umef_export_csv
Hello @scarey149 Thanks for sharing the Network payload, that helped us track this down. The <code class=””>action: umef_export_csv you saw was from a background user-count request, not a CSV export. The preset dropdown is inside the export form, so that hidden field showed up in the payload. The real issue was preset names being sanitized differently on save vs. load (e.g. <code class=””>My Export became <code class=””>my-export), so the preset could not be found after the page refreshed. This is fixed in 1.0.5 (will be released by tomorrow). After updating, hard-refresh the export page (Ctrl+F5 / Cmd+Shift+R) and try loading a preset again. If it still fails, send us the preset name and we will take another look.
Hello @scarey149 Have you tried the latest version? Regards
Tested and working perfectly! Thank you for your speedy fix!!
Hello @scarey149 Great to hear that issues is resolved. Thanks for the revised rating 🙂