Version 6.0.0 is still in beta. Is there anything we could do to resolve the issue in the current version 5.2.1.
By current version you mean version 6.0.0? If it is then is it possible to upgrade from 5.2.1 to 6.0.0 or it will need a fresh install.
Great, I will use EPT with layout paragraphs module for content types.
Additionally, if needed I can also use EBT blocks to put reusable block instances (created individually via block library) in regions of theme or pages if needed.
Many thanks for a detailed and helpful response. Cheers.
I only meant that whether I will be able to add different Extra paragraph types provided by EPT module to an instance (node) of a content type by adding a field of type entity reference revision referencing paragraph types with unlimited values. Whether I can achieve the same purpose which I was trying to achieve with EBT module above by following the steps below but this time with EPT modules:
1) Create a new content type and save.
2) Add a field (for example field name: Page section) of type Entity Reference Revision with the following settings:
a) Allowed number of values: Unlimited.
b) Reference Method: Default.
c) Which paragraphs should be allowed: Include the selected below. Then select all the EPT paragraph types
d) Save the field and content type.
e) Also enable manage layout using Layout Builder.
3) Go and add content of the type created above.
4) Fill title and body field.
5) Add an EPT paragraph (of any available type) and click save.
6) Then add another EPT paragraph (of any available type) to the same content and click save.
7) And then add more EPT of a different type if needed.
Thanks for response. Alternatively, would Extra Paragraph Types module serve the above purpose of inline paragraphs in the content entity.
aanjaneyam → created an issue.
Just wondering if we also have to run the following commands as they are not described in the documentation like other bootstrap themes like Barrio do.
npm install
gulp compile
aanjaneyam → created an issue.
@pingwin_cracow many thanks. Much appreciated.
@pingwin_cracow many thanks for the reply. I was wondering if you could share the final updated version of your composer.json.
Also, how did you update from droopler 3.1.0 to 3.2.0-rc1. The update instructions says uninstall modules lazy and rdf. However, they appear to to be uninstallable because so many droopler and other modules depend upon these two modules. Could lazy and rdf be forcefully uninstalled and if they can be would this un-installation break something else making the upgrade more difficult.
It is weird because if you followed the update.md instructions, you should have version 3.2.0-rc1 instead of version 3.1.0 in your upgrade status messages and it should say it is installed...
@LeDucDuBleuet Thanks. This makes sense. So if I understand correctly, if I follow all the steps mentioned in points 1-6 of updating to 3.2.0 instructions and then run composer update command I should be upgraded to 3.2.0-rc1. Don't we need to make any 3.2.0 related changes to the composer.json before running update command. I mean the update instructions is not very clear. If composer.json needs to be updated/changed before running composer update command then what exactly are the charges that we would need to make to composer.json.
I was of the view that quite a few thing would need to be updated in composer.json including the version of droptica/droopler to 8.3.2.0 and drupal/** to relevant versions.
Same for upgrade from 3.2.0 to 3.3.0 - If composer.json needs to be updated/changed before running composer update command then what exactly are the charges that we would need to make to composer.json.
I can see @pingwin_cracow has made some changes to composer.json in his original post are these all the changes.
Finally at what stage does Drupal Core gets upgraded to version 10. Is it upon running composer update command in version 3.2.0 or 3.3.0.
Simply speaking what are the sequential steps to upgrade droopler and drupal to the latest versions.
@LeDucDuBleuet
You closed my post as duplicate. However, you did not yourself find or mentioned any solution to the problem in your own post. Could you please guide me to what exactly needs to be done to achieve the desired.
@LeDucDuBleuet
Maybe you already know but you can also use the Upgrade status module to better plan your upgrade.
The upgrade status module report says the following
Droopler Profile (droopler)-
Contributed profile Uninstalled 3.1.0 Incompatible N/A 3.3.0-rc1 Incompatible Issues N/A
Why is that?
I was wondering if there are any suggestions or tips on how to fix this issue of sidebars. Is it a bug?