Entering author names with umlauts causes internal server error 500
Virtual Research Environment / On-line Bibliography Manager
Brought to you by:
sirfragalot
Menu
▾
▴
#558 Entering author names with umlauts causes internal server error 500
closed
Bug
8.2
Unknow
Windows
2023-06-19
2023-06-14
No
Workflow:
* Resources > New
* Enter Title
* Enter Publication Year
* Enter new author. Last name should contain an umlaut, e.g. Last name = "Kühn" or "Bundesamt für Naturschutz"
* Save
Now WIKINDX shows the internal server error 500 - problem with the resource - it cannot be displayed.
Despite the error, the resource has been saved.
Workaround:
* Click the back-button of the browser
* Resources > Last List View
* Show resource details: Resource details will be shown without problems.
But:
* Edit ressource title
* Click on Save
* Server error 500 will appear.
Greetings from Stiftung Naturschutz Berlin
Thomas
Many thanks for the report Thomas,
And just in time as we're close to a 6.7.1 release (keep an eye on news etc. here as we'll be releasing a beta version for checking over a couple of weeks).
I'll take care of the bug and will report back here.
Mark
Hi Thomas,
I can't reproduce this and get the result shown in the screenshot immediately after adding a new resource.
Perhaps it's already fixed in the påre-release 6.7.1 which is what I'm working with.
Otherwise, there's some difference between my environment and yours or I'm inputting different data.
Things to check:
1. I created a new resource of type 'book'—same with you?
2. My locale is English (United Kingdom)—have you something else?
3. With the error: 'internal server error 500 - problem with the resource - it cannot be displayed', what is the URL displayed? (You can give the URL following the domain name if you prefer).
Regards,
Markj
Hi Thomas,
I can't reproduce this and get the result shown in the screenshot immediately after adding a new resource.
Perhaps it's already fixed in the pre-release 6.7.1 which is what I'm working with.
Otherwise, there's some difference between my environment and yours or I'm inputting different data.
Things to check:
1. I created a new resource of type 'book'—same with you?
2. My locale is English (United Kingdom)—have you something else?
3. With the error: 'internal server error 500 - problem with the resource - it cannot be displayed', what is the URL displayed? (You can give the URL following the domain name if you prefer).
Regards,
Markj
Hello,
I also cannot reproduce using a book ressource with 6.7.0 and trunk versions, and PHP 8.1 and 8.2.
I am confused. Indeed it may be a problem with a certain type of resource or related to the database engine.
You should activate options "PHP-Fehler und -Warnungen auf dem Bildschirm ausgeben" and "Display SQL statements" and see if an error is displayed.
Regards,
Hello Mark & Stéphane,
thank you very much for your response.
Things to check:
1. Yes, I created a new resource of type 'book' and one of type 'Report/Documentation' - both with the same result
2. We usually work with locale 'Deutsch' but I've switched to 'English' as well with the same result
3. The URL displayed with Internal Server Error 500 is:
http://wikindx-snb/index.php?action=resource_RESOURCEFORM_CORE&type=edit&id=8
(you can see this page from our local server network only - I'v attached a screenshot)
The error does not happen with umlauts in the title or in the firstnames.
I have just discovered that the same error 500 appears when I enter this URL to a ressource: https://locatepress.com/book/dq32
This string has no umlauts but the error happens. The behaviour is a bit strange: I enter the URL only, without URL label and save it -> the error happens. If I add a label "LocatePress" and save it -> the error does not happen. When I delete the label again and press "Save" > the error does not happen. When I delete the URL completely and enter it again without label > the error happens.
Regards, Thomas
Hi Thomas,
Find the log file of your web site / web server and send us an extract containing these errors.
This link could help you: IIS Logs Location.
I will also be curious how WIKINDX works on IIS and what version of IIS you are using. We never tried. Is this a first install?
Regards,
. . . interesting that the ioffending URL is:
http://wikindx-snb/index.php?action=resource_RESOURCEFORM_CORE&type=edit&id=8
which is the URL for the resource editing form.
You should have got:
http://wikindx-snb/index.php?action=resource_RESOURCEVIEW_CORE&messages=&id=8
after successful editing or addition of a resource.
I'm curious why the domain name is just wikindx-snb . . . (no .com, .de, etc.).
When you can successfully edit or add a resource, what's the URL that works?
Mark
Hi,
yes, it is our first install. Our system admin installed WIKINDX. Sorry, I do not have the rights to see or post IIS logs. I'll show him the error - he is already informed.
I don't know why there is no ".de" in our domain name... would have to ask our admin.
After successful editing a ressource the URL it is like it should be:
http://wikindx-snb/index.php?action=resource_RESOURCEVIEW_CORE&messages=&id=4&list=1
Regards, Thomas
Hi again Thomas,
Interesting. But I'm sure we (by which I mean Stéphane) can sort it out. If http://wikindx-snb/... works for a successful edit then I think we can assume that the missing .de is not a problem and is something to do with the IIS server hiding the WIKINDX on the local network.
Do you have rights to configure the WIKINDX from Admin|Configure? If so, do you get any error messages if debugging ('Print PHP errors and warnings to the screen') is turned on?
I will leave this to you Stéphane.
Mark
The TLD (the part missing) is not mandatory on a local area network (LAN).
If you give it the timestamp of the error, it might give you an anonymized excerpt from the log.
If he refuses you can wait for the release of 6.7.1 because we have just added an internal log system to WIKINDX.
You can also export this resource in BibTeX format and send it to us and we could try to import it to raise the same error.
I've attached this and a second ressource in BibTeX format. Both are causing the error.
Importing this file raises a bug [#562]. It could be a lead but it doesn't replace a journal entry. Mark, an idea?
Related
Bugs and feature requests :
#562Last edit: Stéphane Aulery 2023-06-15
I've fixed the bug which was just a warning. I doubt very much it is that. I was wondering if it was something to do with redirection using header(...). Redirection is used after adding/editing a new resource. Perhaps IIS is very picky about redirection.
Mark
I am setting up WIKINDX on IIS 7 on my machine. We will know quickly.
I created a book resource with a title only and found this error:
[15-Jun-2023 21:58:08 Europe/Paris] PHP Deprecated: preg_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in C:\inetpub\wwwroot\core\modules\resource\RESOURCEWRITE.php on line 1401
In fact you fixed it with [r4138] Mark.
Related
Commit: [r4138]
I found another fixed by [r3743].
Related
Commit: [r3743]
Thomas,
After several tests I think you are encountering errors related to PHP 8.2 support. They are already corrected for the next release 6.7.1. While waiting for the publication, I recommend that you apply the patch attached (overwrite the core folder of your installation with that of the zip to apply the corrections).
This should fix:
Regards,
Last edit: Stéphane Aulery 2023-06-15
Warm thanks to you, Stéphane! I passed your message on to our admin.
Glad to help. Let us know if this patch fully resolves the 500 error. And welcome aboard.
Great! Our Admin Andreas has installed your patch now. A quick test was successful - authors with umlauts are accepted now as well as ressources with title only. Thank you very much again, Stéphane and Mark!
Hi Thomas,
Glad it works. The patch does not contain the correction of all the errors related to PHP 8.2, in particular the Ideas plugin. In a few weeks version 6.7.1 will correct these last errors.
Regards,