Cannot directly upload to Scribd anymore [simplexml_load_string() error]
ff2d - December 28, 2008 - 00:30
| Project: | iPaper |
| Version: | 6.x-1.0-rc2 |
| Component: | User interface |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Hi, I'm new to Drupal and I'm developing a local website using XAMPP. I was happily uploading many documents through the iPaper module. Everything was working fine then suddenly I couldn't successfully upload files anymore. When I create a new iPaper content, the node is created but the document attached is not converted to iPaper and I receive these error messages all at once:
* warning: simplexml_load_string() [function.simplexml-load-string]: Entity: line 1: parser error : Start tag expected, '<' not found in C:\Programmi\xampp\htdocs\mywebsite\sites\all\modules\ipaper\scribd.php on line 239.
* warning: simplexml_load_string() [function.simplexml-load-string]: Status: 500 Internal Server Error in C:\Programmi\xampp\htdocs\mywebsite\sites\all\modules\ipaper\scribd.php on line 239.
* warning: simplexml_load_string() [function.simplexml-load-string]: ^ in C:\Programmi\xampp\htdocs\mywebsite\sites\all\modules\ipaper\scribd.php on line 239.
* Scribd error #:It seems like it just stopped working. I tried to refresh the module files but didn't help. Then I tried adding the iPaper module to another local drupal installation I have and I received the same error messages when trying to upload.
I need the direct file upload for the people I'm developing the website for, so it's kind of a problem.
Any idea? Thank you :-)
#1
It seems like the requests to Scribd are not succeeding. Do you have CURL installed or is fsockopen supported on your server?
#2
also, can you make sure you have php5?
#3
I'm creating release candidate 4 that might solve this problem. Can you check if it fixes your problem?
#4
30 weeks and no answer... should we mark this fixed?
#5
yes, this was probably either fixed with the new releases, or the issue was related to something on that specific server.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.