After installing silverstripe-elemental: composer require dnadesign/silverstripe-elemental, and adding the below into app/_config/elements.yml, I am not able to see the “Select Page Type dropdown” in CMS. I have tried logging off and in again, restart MAMP and nothing works.
Can you successfully run a composer update without errors?
Yes, no errors, kindly refer below:
> composer update
Loading composer repositories with package information
Updating dependencies
Nothing to modify in lock file
Installing dependencies from lock file (including require-dev)
Nothing to install, update or remove
Generating autoload files
63 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
Time: 6 secs
Can you confirm the version of Elemental that is installed? (with composer info dnadesign/silverstripe-elemental)
Kindly refer below:
> composer info dnadesign/silverstripe-elemental
name : dnadesign/silverstripe-elemental
descrip. : Elemental pagetype and collection of Elements
keywords : Content Blocks, element, elemental, silverstripe
versions : * 5.3.9
released : 2025-02-27, 2 weeks ago
type : silverstripe-vendormodule
license : BSD 3-Clause "New" or "Revised" License (BSD-3-Clause) (OSI approved) https://spdx.org/licenses/BSD-3-Clause.html#licenseText
homepage :
source : [git] https://github.com/silverstripe/silverstripe-elemental.git c385dc820a56ba89b835e3b6d00eadfeb6792f23
dist : [zip] https://api.github.com/repos/silverstripe/silverstripe-elemental/zipball/c385dc820a56ba89b835e3b6d00eadfeb6792f23 c385dc820a56ba89b835e3b6d00eadfeb6792f23
path : /Applications/MAMP/htdocs/silverstripecms/silverstripe-01/vendor/dnadesign/silverstripe-elemental
names : dnadesign/silverstripe-elemental
support
issues : https://github.com/silverstripe/silverstripe-elemental/issues
source : https://github.com/silverstripe/silverstripe-elemental/tree/5.3.9
autoload
psr-4
DNADesign\Elemental\ => src/
DNADesign\Elemental\Tests\ => tests/
requires
php ^8.1
silverstripe/admin ^2.0.1
silverstripe/cms ^5
silverstripe/framework ^5.3
silverstripe/graphql ^5
silverstripe/vendor-plugin ^2
silverstripe/versioned ^2
silverstripe/versioned-admin ^2
symbiote/silverstripe-gridfieldextensions ^4
requires (dev)
phpstan/extension-installer ^1.3
silverstripe/documentation-lint ^1
silverstripe/frameworktest ^1
silverstripe/recipe-testing ^3
silverstripe/standards ^1
suggests
dnadesign/silverstripe-elemental-subsites Adds subsite support to elemental
dnadesign/silverstripe-elemental-userforms Adds userform support to elemental
dnadesign/silverstripe-elemental-virtual Adds support to share blocks between pages
silverstripe/elemental-blocks Adds a set of common SilverStripe content block types
silverstripe/fulltextsearch Adds fulltext search capability for elements using Solr
>
Does the dev/build show any information or errors?
Kindly refer below:
Do you have any other modules installed which could be affecting things?
No, I have not installed any other module.
When you ran the initial dev/build were there any Element tables created (or can you check that they’re actually present)?
Yes, the Element table is present, kindly refer below:
If you run sake dev/config or go to /dev/config in your browser, do you see the extension being applied? This lets you check if the configuration is actually applying to the page class or not.
The whole output is too huge to attached but here is one of the sections that contains “DNADesign”, I am not sure if this section is where we can tell if the configuration has been applied, but do let me know if there is a particular keyword to look out for. Thanks.
I’m not asking you to put the output here, but just to look at the output for yourself. This is the configuration that gets applied from all that YAML - so you should be able to find the ElementalPageExtension being applied to the extensions config on Page in the output if it’s being applied.
That seems to me like your configuration in app/_config/elements.yml hasn’t been applied.
Reasons that might cause that (which I think are all unlikely in this case) include:
You haven’t flushed
You’re looking at the wrong site or environment (e.g. changing in dev, but looking at a separate test environment, or changing site 1 and looking at site 2)
If you’re using virtualisation (very unlikely with MAMP), there’s a desync between the virtual and real file system
You’ve misspelled _config for the directory name
You’ve put the config inside --- metadata jail
As I said I don’t think any of those are likely the problem in your case, but should be quick for you to rule out.
Some ways that might help you get moving forward (they won’t fix whatever underlying problem is stopping your config from being picked up but should let you continue for now) include:
If you have another configuration file that is working as expected, try putting the extension configuration into that file instead.
You can apply extensions in your Page.php file by setting the private static array $extensions configuration property, instead of YAML.
Hi, I have tested a few PHP & MySQL combinations and found that it is PHP version 8.2.27 that is causing the issue on my machine:
PHP 8.1.31 + MySQL 5.6.51 - Works
PHP 8.1.31 + MySQL 5.7.44 - Works
PHP 8.2.27 + MySQL 5.6.51 - Fail
PHP 8.2.27 + MySQL 5.7.44 - Fail
PHP 8.3.16 + MySQL 5.6.51 - Works
PHP 8.3.16 + MySQL 5.7.44 - Works