Cannot create new feed

@icedo,

Thank you for using our plugin and reaching out to us. Sorry to hear that you are experiencing issues with it. I need your help to understand what exactly is going wrong.

Could you go to the “Manage feeds” page and add this to your URL &debug=true

Your URL should look something like this now:
….wp-admin/admin.php?page=woosea_manage_feed&debug=true

On the screen you should now see a box with a red line on the left side. Could you copy / past the content of that box and e-mail it to me on support@adtribes.io? It will help me to understand how exactly you have configured your product feeds and what the processing status of them is.

Thank you very much.

All the best,
Joris

@icedo as you did not respond I assume the issue has been solved or is not that urgent anymore. I will therefor close the issue for now. Please let me know if you need more help.

All the best,
Joris

No,

it’s not solved. the problem is still here. i can’t use your plugin.

I sent you the mail some days ago.

But i don’t have a lot of time to resolve this at the moment.

Regards.

Same problem. Latest WP and plugin. I’m getting blank page when choosing Custom Feed.
No PHP errors, JS error: TypeError: $(…).dialog is not a function.

Please help. Thanks.

@jamie512

Thanks for reaching out, sorry to hear you are experiencing issues.

In what step of the configuration are you getting the blank screen? On the last page (Add Google Analytics tracking) after you press the button ‘Generate product feed’?

Also, do you know what PHP version you are running?

All the best,
Joris

Product Feed Pro -> Create feed ->
Project name: Test
Channel: Custom Feed
File format: XML

Save & continue, and then nothing – without errors, just a blank page.

[PHP] => 7
[Wordpress] => 4.8.2
[WooCommerce] => 3.2.1

@jamie512,

Thanks for this extra information.

I just discovered that the plugin was not forced to retrieve new versions of my javascript and CSS whenever I made changes to it. Changes are that it used really old stylesheets and javascript that did not contain any of the fixes I did the last couple of weeks. I now fixed that bug and released a new version (1.6.6) of the plugin. There is a small change that is solves your issue. Could you give it a try?

Thanks!
Joris