View Issue Details

IDProjectCategoryView StatusLast Update
0006993OXID eShop (all versions)2.4. Administer productspublic2019-11-12 08:58
Reporterpbenke Assigned To 
Status resolvedResolutionfixed 
Product Version6.1.1 
Fixed in Version6.2.0-rc.1 
Summary0006993: Wrong format in external url on article input
DescriptionFor example:
Stored value in database in oxarticles.OXEXTURL:
The form will show http://


=> line 133
input ... name="editval[oxarticles__oxexturl]" value="http://[{$edit->oxarticles__oxexturl->value}]"...
(Look at value)
Steps To ReproduceInput an article with an external url (tab "Erweitert")
TagsAdmin Template, Article
ThemeNot defined
PHP VersionNot defined
Database VersionNot defined



2019-06-12 13:23

administrator   ~0012913

Last edited: 2019-06-12 13:24

Thanks for your report. I agree that the form is showing a wrong URL since it always adds "http://" to the beginning, but unlike your description I don't run in any issue with that behavior present.

I did the following:
1) Chose an article.
Extern URL form field shows "http://".
Database field shows "".
2) Filled in the url
3) Saved.
Extern URL form field shows: "http://".
Database field shows "".
4) Saved again.
Extern URL form field still shows: "http://".
Database field still shows "".

Therefore the form doesn't look good, but the behavior have not led into a problem with the saved value. The URL is stored correctly in the database even after resaving. As a result I have acknowledge your issue as a bug because the form shows a wrong value. But since the mechanism isn't affected, I've edited the issue description and set the priority to low.



2019-06-12 13:36

reporter   ~0012914

Thanky you,
sorry, I reported not everything.

The error occurs in Frontend!

Please have a look inside the wrong template:
Line 12

Thank you.


2019-06-12 14:43

administrator   ~0012915

Please specify your concern. The link in the shop frontend works fine in my testing environment.



2019-06-12 15:00

reporter   ~0012916

Sorry, my fault.
Has been already fixed in the last Flow theme version.

Thank you.