Hey there, Awesome Customers!

Just a heads up: We'll be taking a breather to celebrate International Workers' Day (May 1st and 2nd - Wednesday and Thursday) and Orthodox Easter from Good Friday (May 3rd) through Easter Monday (May 6th). So, from May 1st to May 6th, our team will be off enjoying some well-deserved downtime.

During this time, our customer support will be running on a smaller crew, but don't worry! We'll still be around to help with any urgent matters, though it might take us a bit longer than usual to get back to you.

We'll be back in action at full throttle on May 7th (Tuesday), ready to tackle your questions and requests with gusto!

In the meantime, you can explore our documentation for Amelia and wpDataTables. You'll find loads of helpful resources, including articles and handy video tutorials on YouTube (Amelia's YouTube Channel and wpDataTables' YouTube Channel). These gems might just have the answers you're looking for while we're kicking back.

Thanks a bunch for your understanding and support!

Catch you on the flip side!

Warm regards,

TMS

Okay
  Public Ticket #2856512
Continuously getting Internal Server Error
Closed

Comments

  • Ed Schmidt 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 Schmidt 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 Schmidt 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 Schmidt 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 Schmidt 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 Schmidt 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.