We're Moving to a New Support Platform – Starting June 1st!

We’re excited to let you know that starting June 1st, we’ll be transitioning to a new support system that will be available directly on our product websites – Amelia, wpDataTables, and Report Builder. In fact, the new support platform is already live for Amelia and wpDataTables, and we encourage you to reach out to us there.

You'll always be able to reach us through a widget in the bottom right corner of each website, where you can ask questions, report issues, or simply get assistance.

While we still do not offer live support, a new advanced, AI-powered assistant, trained on our documentation, use cases, and real conversations with our team, is there to help with basic to intermediate questions in no time.

We're doing our best to make this transition smooth and hassle-free. After June 1st, this current support website will redirect you to the new "Contact Us" pages on our product sites.

Thanks for your continued support and trust – we’re excited to bring you an even better support experience!

Okay
  Public Ticket #2856512
Continuously getting Internal Server Error
Closed

Comments

  • Ed started the conversation

    I've tried with both a CSV and XLS file, but I keep getting Internal Server Error. Host has checked the error logs and found nothing. They suggested contacting you, as they claim it is an issue with the plugin.

  • [deleted] replied

    Hi Ed

    Thank you for reaching out to us.

    This usually happens if the source file is not formatted correctly.

    Please note that there are some limitations when using Google spreadsheets to create tables in wpDataTables. Formatting applied in the original file (font families, color, size, fill color, etc.) will not be copied over to the wpDataTable, but you can make whatever adjustment you may need in WpDataTables.

    Please refrain from using any special formatting in the source file as the plugin may not be able to read the data properly and may result with an error.

    Also please provide us with some screenshots or a screen recording of the issue and the source file used to create the table so we can try and recreate the issue.

  • Ed replied

    Hi Blaženka,

    Thank you for your reply... since I've tried both XLS and CSV formatted files and still get the same error, I'm thinking that it's not a formatting issue; CSV file is pretty much just text, no?

    Thank you,

    Ed


  • [deleted] replied

    Hi Ed

    Also please provide us with some screenshots or a screen recording of the issue and the source file used to create the table so we can try and recreate the issue.

  • Ed replied

    Hi Blazenka,

    I've attached a screen recording -- please let me know if I'm doing this correctly. Hope this helps.

    Thanks,

    Ed

  • Ed replied

    Oh, and the xls file

    Thanks,

    Ed

  • [deleted] replied

    Hi Ed

    This is how the file looks like when we try to open it, there are no headers in the table, the data is all scrambled and there seems to be some custom formatting applied which should be removed.

    Please have a look at the example document and reformat your table accordingly

    https://wpdatatables.com/documentation/creating-wpdatatables/creating-wpdatatables-from-excel/

    4659265326.png


  • Ed replied

    Wow... that is a mess. I'll need to look into fixing it. Since I didn't create it, perhaps I can revise or reformat and try again. Thanks for your help!

  • [deleted] replied

    You are most welcomesmile.png

    If there is anything else we can assist you with please don't hesitate to open a new ticket.

    Have a wonderful day! 

  • Ed replied

    Hi Blazenka,

    Thank you for your insight about my XLS file. I've reformatted it and am now getting a different error:
    Bad gateway

    What do you suppose that means?

    Thanks!

    Ed


  • [deleted] replied

    Hi Ed,

    thank you for contacting backsmile.png

    A 502 Bad Gateway Error is a general indicator that there's something wrong with a website's server communication. Since it's just a generic error, it doesn't actually tell you the website's exact issue. 

    You would need to reach out to your server hosting to check with them where did the communication stop / was blocked.