stevesi

sorry – I have been busy and I decided to disable the plugin as I don’t have time to test just now and I am not experienced in testing plugins/wordpress etc. Thanks for the fix. I will report back when next release if still an issue. sorry.

warning: use of undefined constant sfsi_plus_domain – assumed ‘sfsi_plus_domain’ this will throw an error in a future version of php

I get same error.

Hi, I was still getting this error until just now.
If I add a new FAQ (URL is https://easy2boot.xyz/wp-admin/post.php?post=492&action=edit) and then Publish it. I can keep that browser page open but also go into WP panel and click on Edit for the same FAQ page. It then loads the exact same page with same URL in a new browser window. The only difference is that the text in the Browser TAB says ‘Add New FAQ < Easy2Boot — WordPress’ but the non-working tab says ‘Edit FAQ “Windows install ISO < Easy2Boot’ even though URL is the same.
I can edit the text in the Add new page, but as soon as I dob the cursor on any portion of text on the Edit FAQ page I get the error.

I then changed two things.
1. I have a FooBox plugin – I ticked the box to disable it on that page. It did not appear to have any effect on the error on the ‘bad’ browser page.
2. I noticed that Chrome was prompting me to translate the page from Arabic to English. I ticked the ‘never translate this page’ option and there is now no error on either page. Even if I untick the ‘never translate this page’ option I still get no error.

So not sure what fixed the issue, but I will let you know if it comes back or I have any more news.

Any ideas where to look. Could another plugin be causing a problem? If so any guess as to the type of plugin?

P.S. I also cannot add a new group from the Edit page – right-hand side pane for ‘FAQ’ – Add New FAQ Group. When I click on ‘Add New FAQ Group’ button the new group name is not added to the list. However, I can add a new group from the Panel Settings plugin page for FAQ.

I have updated. Same issue.
Any idea how to fix?

Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Sh (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:152:165)
    at Qj (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:174:181)
    at unstable_runWithPriority (https://easy2boot.xyz/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:24:26)
    at Za (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:8)
    at eb (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:170:163)
    at gf (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:162:317)
    at https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:230
    at unstable_runWithPriority (https://easy2boot.xyz/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:24:26)
    at Za (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:8)
    at $g (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:176)

Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at Sh (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:152:165)
    at Qj (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:174:181)
    at unstable_runWithPriority (https://easy2boot.xyz/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:24:26)
    at Za (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:8)
    at eb (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:170:163)
    at gf (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:162:317)
    at https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:230
    at unstable_runWithPriority (https://easy2boot.xyz/wp-includes/js/dist/vendor/react.min.js?ver=17.0.1:24:26)
    at Za (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:8)
    at $g (https://easy2boot.xyz/wp-includes/js/dist/vendor/react-dom.min.js?ver=17.0.1:73:176)

As soon as I put editor cursor in content text when editing, it crashes and gives me option to Attempt Recovery Copy Post Text Copy Error

I can edit title of FAQ but not content.

Thanks for reply
If I was a hacker, I would delete all font html entries to remove any weird fonts and allow OCR to work…

If the bot has ocr, then why not ask the user to use lowercase only and deliberately block any response that has exactly the same case as all the letters entered, i.e. identical. That way even ocr bots are blocked.

Meanwhile change your background page colour to be a very light grey, then you can see the caption. You can change the background back to white after editing all pages.

I was hoping someone cleverer than me would read our posts and fix the issue!

Did you change the text colour of the caption text?
You first have to find the caption text empty box which is like playing battleships because you have to click on the blank space under the image where the caption text box should be if only you could see it. If there is text already there then you need to highlight the existing caption and then set the colour to black.
1. click on image – you see it is selected
2. move cursor down to where caption should be (cursor changes from arrow to I-beam cursor in Edge and Chrome)
3. click – now you should see the small floating caption box for B I <link> v
(bold italic link more)
4. Once you get the caption edit control box visible, move the cursor to just below it in the approx middle of the screen (empty white space) until you get the I-beam cursor and hold down the left-mouse button – now move the mouse to the left and it should highlight the current caption text (background colour will depend on your theme – I use Astra).
5. After selecting caption text, click on v down-arrow of the floating caption edit control and select ‘text color’
6.Click on Black colour (even though it is already selected)
now the text should remain visible in the editor (but only for that image).
HTH

• This reply was modified 3 years, 6 months ago by stevesi. Reason: add detail steps
• This reply was modified 3 years, 6 months ago by stevesi.

In Chrome F12 mode, I can see a

.wp-block-image figcaption {
  color: #555;
  font-size: 13px;
  text-align: center;
}

but the color and text lines are struck through.
I can change the font-size and the caption space increases, so the text is getting larger but the color setting seems to be ignored if I try to change it.

• This reply was modified 3 years, 6 months ago by stevesi.

<figcaption role=”textbox” aria-multiline=”true” aria-label=”Image caption text” class=”block-editor-rich-text__editable rich-text” contenteditable=”true” style=”white-space: pre-wrap;”>E2B Launcher will help you use your new E2B USB drive</figcaption>

This is what I see if I inspect the image element in Chrome on the Gutenberg edit page