- Issue created by @SirClickALot
- 🇩🇪Germany a.dmitriiev
Please share the Drupal and Gin Theme versions that you are using.
- 🇬🇧United Kingdom SirClickALot Somerset
Sorry, that was sloppy on my part.
Drupal 10.3.6
Gin 8.x-3.0-rc13 - Merge request !86Issue #3481210 by a.dmitriiev: Action buttons missing on nodes with Gin theme → (Merged) created by a.dmitriiev
- 🇩🇪Germany a.dmitriiev
Please check the MR. The buttons should be now there.
-
a.dmitriiev →
committed 7471722c on 2.x
Issue #3481210 by a.dmitriiev: Action buttons missing on nodes with Gin...
-
a.dmitriiev →
committed 7471722c on 2.x
- 🇬🇧United Kingdom SirClickALot Somerset
I can confirm that merge request !86 deals with the issue perfectly.
-
a.dmitriiev →
committed 40f8e8a0 on 1.x
Issue #3481210 by a.dmitriiev: Action buttons missing on nodes with Gin...
-
a.dmitriiev →
committed 40f8e8a0 on 1.x
- 🇬🇧United Kingdom SirClickALot Somerset
Now that we have this all working according to the above fix for the action buttons, we have started using it more but have come across some odd behaviour when it does not appear to update the Body field of a node.
Here is the illustrated story so far...
STEP 1: Adjust FEE configuration so that Content > Tutorial (content type) is enable.
STEP 2: Attempt to edit through the front end...
STEP 3: Perform the edit in the off-canvas sidebar...
STEP 4: We see two clear node update confirmation messages....
and from the Watchdog...
In this second screenshot, you can also see some ECA actions (2 and 3) being performed and at first we thought it might be connected so we disabled the ECA action that targets the Tutorial content type but that had no effect - still no success in FEE editing.
Likewise, we also had a line or two of custom hook also processing updates on the Tutorial content type so we disabled that too but again, it had no effect.
STEP 5: Check the rendered page to see that the field has not been edited...
There is nothing relevant in the Watchdog and nothing in the JavaScript Console.
Now of course we're not expecting anyone to be able to debug this given only those illustrations but we would be interested in anyone's ideas as to what exactly to check next in order to try to get to the bottom of this oddity?
Confirmations
We never have any trouble with Paragraph editing with that, or any other nodes, it's edit (in this case the Body field) that is the problem.
Secondly, we can also confirm that editing the node through the conventional backend works fine.
Thirdly, and most strange of all, we can edit other nodes through the FEE front perfectly successfully; it seem as though it might somehow be limited to editing this one particular content type.
We have been quite involved in feedback on this module over the last year or so because we are keen to champion its use and so if it's useful to the core maintainers we would be happy to DM and link up on a call and thrash it out - we just wanted to start the dialogue today in case we are missing something really obvious.
Drupal 10.3.6 Apache/2.4.33 (Win64) OpenSSL/1.0.2u mod_fcgid/2.3.9 PHP/8.3.1 PHP 8.3.7, memory limit: 256M MySQL 5.7.24 PHP Caching module: OpCache Web browser: Version 127.0.6533.89 (Official Build) (64-bit) Front end theme A custom subtheme Bootstrap5 (Bootstrap5 3.0.10) FEE module 1.8.2
Thanks all.
- 🇩🇪Germany a.dmitriiev
@sirclickalot please create another issue for this. It is getting hard to focus on the problem if you post in the comment of the issue that was obviously a problem of form display in Gin and now you Post a problem with some node save and ECA integration. This has to be in its own issue. This issue is fixed.
- 🇬🇧United Kingdom SirClickALot Somerset
Yes of course, you are quite right.
Done: https://www.drupal.org/project/frontend_editing/issues/3484037 🐛 Body fields not being updated in some scenarios Active Automatically closed - issue fixed for 2 weeks with no activity.