Categories
View Replies (22)

Resolved import shows blank screen and fails to run

  1. johnf
    johnf
  2. RO CSVI
  3. Wednesday, 16 September 2020
  4.  Subscribe via email
CSVI version: 7.17.0
Joomla version: 3.9.21
PHP version: 7.3.22

I am in the process of migrating an existing website to a new server. Currently the new server is running under an IP address only as I am not transferring the domain name until setup and configuration is complete and I have finished testing the new site. I have quite a few import routines that I created using CSVI and nearly all of them work fine on the new site as well as the old site. However, there are two import routines that read the same source file on the new site and both fail to run. They continue to work on the original site. The only difference I can spot is that the Joomla version on the original site is 3.8.18.

I have attached the debug log (which stops at the first record) and a copy of one the templates involved. I will say that you helped solve an issue with this source file over a year ago and it is documented in this forum - it should be easy to find as I only have two previous threads on this forum. Here is a link to the source file

Thanks,

John
Attachments (2)
csvi_templates_162.214.145.66_20200916.xml
com_csvi.log.12.zip
0
Responses (22)
johnf
johnf
Accepted Answer Pending Moderation
Hi Tharuna and RolandD,

Thank you for your help with this tricky problem. I reviewed the server configuration yesterday and was unable to find anything that could be causing this issue. All other CSVI imports work and in fact the entire extensive site works as expected on this server with the exception of the import of this one file using CSVI.

I decided to take a different approach to solving this yesterday as it has been too long and no progress was being made towards a resolution by looking at the server configuration or the CSVI program. I downloaded and installed the PHPSpreadsheet library and installed it on my server. Then, I wrote some PHP code that utilizes the PHPSpreadsheet library to convert the problematic XLS source file to CSV format. Next, I changed my CSVI configuration for this import to CSV from XLS. This solves the problem although it was not a simple workaround.

I also am not convinced that CSVI is not the cause of this issue. While I understand that it may be difficult or even impossible to diagnose and resolve a problem that cannot be recreated on a different server, this does not mean that there is no issue with CSVI in this case. My new PHP script that uses the PHPSpreadsheet library to convert the XLS file has no trouble opening, parsing and converting the problematic XLS source file on my server (CSVI can't even open the file). As I said before, there are no other errors that occur on my server with CSVI or any of the other programs that are installed. Finally, a 500 error is pretty meaningless as it simply means the system can't really determine what went wrong other than the fact that it happened on the server! This does not necessarily mean it is an error caused by the server.

Thanks again for your help and patience trying to resolve this issue. I appreciate it!

Kind regards,

John
  1. more than a month ago
  2. RO CSVI
  3. # 21
rolandd
rolandd
Accepted Answer Pending Moderation
Hello John,

It is good to hear that you get things running but I do agree it is cumbersome. However what is ironic is that in RO CSVI we also use PHPSpreadsheet to parse XLS files. You can find it in the folder administrator/components/com_csvi/assets/spreadsheet_reader.

Finally, a 500 error is pretty meaningless as it simply means the system can't really determine what went wrong other than the fact that it happened on the server!
In case of a 500 error, a server is usually configured to only write the error to the system error log. Without the actual error message it is looking for a straw of hay in a haystack :p

This does not necessarily mean it is an error caused by the server.
Agree with that because we have no clue what is causing it. The only way to get anything on this is to get the actual error generated on the server.
Kind regards,

RolandD

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 22
  • Page :
  • 1
  • 2


There are no replies made for this post yet.
Be one of the first to reply to this post!