Images uploaded thru the WYSIWYG editor are getting the full FQDN attached to them and are being filtered somehow (FaqSanitizer? HTMLSanitizer?)
If I manually edit the source code of the article and remove the FQDN and use relative img src (image/IMAGENAME.jpg instead of https://fqdn/images/IMAGENAME.jpg) tags to the image file, the file shows properly.
The above problem is isolated to the article view by the end user, not modification or admin. The images show in modification/edit screen.
phpMyFAQ version (3.2.0)
PHP version (8.1.2-1ubuntu2.14)
Database (MySQL 5.7.42-0ubuntu0.18.04.1-log)
Elasticsearch Not used/installed
OS: Any (test on Steamdeck (Arch/Valve), Win10 and Win11)
Browser Any (tested on Edge, Chrome, Braver, Firefox)
Additional context
I think the problem is related to the FaqSanitizer/HTMLSanitizer problem on another bug report/issue thread (#2615 and #2588)
I THOUGHT the problem was because we upgraded phpMyFAQ and the host OS a dozen times over the years causing problems. But I built an entirely brand new VM image running Ubuntu 22.04 LTS fully up to date and was able to duplicate the entire scenario.
I have 'before and after' modification of the source code for the article to make the images work if you would like it for bug reporting purposes.
Images uploaded thru the WYSIWYG editor are getting the full FQDN attached to them and are being filtered somehow (FaqSanitizer? HTMLSanitizer?) If I manually edit the source code of the article and remove the FQDN and use relative img src (image/IMAGENAME.jpg instead of https://fqdn/images/IMAGENAME.jpg) tags to the image file, the file shows properly.
The above problem is isolated to the article view by the end user, not modification or admin. The images show in modification/edit screen.
phpMyFAQ version (3.2.0)
PHP version (8.1.2-1ubuntu2.14)
Database (MySQL 5.7.42-0ubuntu0.18.04.1-log)
Elasticsearch Not used/installed
OS: Any (test on Steamdeck (Arch/Valve), Win10 and Win11)
Browser Any (tested on Edge, Chrome, Braver, Firefox)
Additional context I think the problem is related to the FaqSanitizer/HTMLSanitizer problem on another bug report/issue thread (#2615 and #2588) I THOUGHT the problem was because we upgraded phpMyFAQ and the host OS a dozen times over the years causing problems. But I built an entirely brand new VM image running Ubuntu 22.04 LTS fully up to date and was able to duplicate the entire scenario.
I have 'before and after' modification of the source code for the article to make the images work if you would like it for bug reporting purposes.