Editor: BBC Code Icons do not work

[RainerBielefeld]

"Houston ..."
In one of my 4 Flatpress installations (1x 1.3.1 and 3x Master 1.5) BBC Code Icons do not work
Same for Blog Entries or Comments

STR

1. Visit My Config
2. Click Kommentar hinzufügen
   » Comment Editor opens
3. "Type 1234" into the Text Input Area
4. Click most left simley
   » Expected: Smiley Code inserted
   » Actual: Nothing inserted, Text input Area becomes grey

Additional Info
a) Toggling Themes or Languages changes nothing.
b) In an other 1.5 Master installation Commenting with those Code Icons works fine
c) icons look different in working and not working – Source code for that area is completely different between both installations, details see http://foss.weststadtaktivkasse.de/myfp ... -not-work/!
d) Both Installations have installed Comment Center Plugin 1.1.4

Of course you may do your own test in My Config

Your recommendations for more analytics or a Fix?

CU

Rainer


---

[fraenkiman]

Hi Rainer,

Clear your browser cache, try a different browser if necessary, or try a different device if necessary.

Best regards,
Frank

[RainerBielefeld]

Of course I tested in different Browsers before I asked here.

Firefox
148.0a1 (2025-12-18) (64-Bit) On Win 10

Chromium
Version 130.0.6701.0 (Entwickler-Build) (64-Bit) On Win 10

EDGE
Version 143.0.3650.80 (Offizielles Build) (64-Bit) On Win 10

SeaMonkey
Version 2.53.22 beta 1 On Win 10

And of course with deleting Browser cache

And just for fun today also FF 144.0 (64-Bit) on Linux Mint. With the predictable result: doesn't work either.

But unfortunately I am pretty sure that you did not do an own test following my STR ...

Can someone please do that test and tell his thoughts?

CU

Rainer

[RainerBielefeld]

Some more Test results

Copy of the Blog works fine
I created a copy of the Blog with the problem. Simple ftp copy of all folders and all files to here

And strange: there Icons in Edit mode work perfectly

I'll leave [ur=https://bielefeldundbuss.de/FlatPress_RainerSeiner/l]the original Blog[/url] at it's place without changes because more tests concerning the observed problem might give hints concerning a problem with Flat Press 1.5. Which only appears under very particular circumstances. I doubt, but you never know.

Then I will start repair attempts

[fraenkiman]

Hello Rainer,

In FP 1.3.1, there were still some insecure JS-HTML methods, which I removed starting with 1.4.X.

Screenshot 2025-12-20 131006.png (67.64 KiB) Viewed 219 times

Perhaps you mixed up versions? If so, try to avoid doing that. Do not attempt to use plugins from a higher FP version in an older FP version.

Best regards,
Frank

[RainerBielefeld]

In FP 1.3.1, there were still some insecure JS-HTML

Hi Frank,

the problem is in a 1.5.Master Blog, as you see when you follow my Steps to Reproduce in the original posting here. In the linked Blog showing the Problem Step 1 "Visit My Config"

And the question is – Why and how does the problem disappear in a 1:1 copy oft the complete blog to a different folder on the same server?

CU

Rainer

[fraenkiman]

You need to straighten out the ownership/directory and file permissions.

Code: Select all

// For the directory fp-content and its subdirectories including the files
FILE_PERMISSIONS 0644 is recommended
DIR_PERMISSIONS 0755 is recommended

// FlatPress core: This includes this file, recursively the directories ADMIN_DIR, FP_INCLUDES, CONFIG_DIR, USERS_DIR, LANG_DIR, SHARED_TPLS and PLUGINS_DIR
CORE_FILE_PERMISSIONS 0640 for productive operation
CORE_DIR_PERMISSIONS 0750 for productive operation

// For all other files and directories, e.g. FP_INTERFACE, THEMES_DIR
RESTRICTED_FILE_PERMISSIONS 0644 is recommended
RESTRICTED_DIR_PERMISSIONS 0755 is recommended

Usually, www-data is the owner; however, this may differ on shared web hosts. See cPanel.

[RainerBielefeld]

Problem ist gelöst
Es waren falsche Chmod-Berechtigungseinstellungen.

Warum das nur bei einer von 4 Installationen auftrat versuche ich demnächst noch mal zu ergründen, sieht aber eher nicht wie ein Flratpress-Problem aus.

CU

Rainer