Splitted from https://github.com/bolt/four/pull/148

• [x] I really don't like all those "magic" methods in ContentMagicTrait. Can we at least rename them to be less magical? :)
• [x] if we could make $this->fields a name-indexed array, using this method be much faster (simple isset instead of foreaching).
• [x] rename to get to getField, has to hasField

I have a repeater in my contenttype in Bolt v3 like so:

        features:
            type: repeater
            fields:
                title:
                    type: text
                image:
                    type: image
                    extensions: [ gif, jpg, png ]
                teaser:
                    type: text
                    class: large
                content:
                    type: html   

Thereby in my contenttype I can add a new feature which includes a title, an image, a teaser and content. Now, I would like to have the same in v4, but I saw that repeaters do not longer exist. I tried to achieve the same functionality by changing the type from repeater to collection. But then, I can only add the different fields one by one and that is not what I want. I would like to have the exact same functionality of a repeater of v3 in v4. Do I need to use a set? I did not find an example how to do this in the docs.

Thank you in advance

I've just installed a fresh copy of the latest Bolt but I get a 404 error when loading the site. Like this:

404 :: Content not found

In Controller/TwigAwareController.php

Symfony\Component\HttpKernel\Exception\NotFoundHttpException {#5565 ▼
  -statusCode: 404
  -headers: []
  #message: "Content not found"
  #code: 0
  #file: "/.../myprojectname/vendor/bolt/core/src/Controller/TwigAwareController.php"
  #line: 123
  trace: {▶}
}

I followed the instructions in the docs to install via composer, i.e. I ran these:

composer create-project bolt/project myprojectname
(edit .env with correct MySQL parameters)
chmod -R 777 config/ public/files/ public/theme/ public/thumbs/ var/
bin/console doctrine:database:create
bin/console doctrine:schema:create
bin/console bolt:add-user --admin

Opening the home page via my server, or using the built-in server, I get a 404.

Details

| Question | Answer |----------------- | ------ | Relevant Bolt Version | 4.0 | Install type | Composer | PHP version | 7.2.33 | Web server | Apache or Built-in, both fail

We have content with a collection of sets like this:

slides:
    name: Slides
    singular_name: Slide
    ....
    fields:
        .....
        popups:
            type: collection
            fields:
                afbeelding:
                    type: set
                    fields:
                        label:
                            type: text
                        weergave:
                            type: select
                            values: [ 'beeldvullend', 'kleine tooltip' ]
                        afbeelding:
                            type: image
                tekst:
                    type: set
                    ....

The nested select field has been added after content had already been created. (I don't know if this is relevant)

Now when we edit content and add a 'popup' the editor will get a 500 error:

TypeError:
explode() expects parameter 2 to be string, null given

  at vendor/bolt/core/src/Twig/FieldExtension.php:255
  at explode('/', null)
     (vendor/bolt/core/src/Twig/FieldExtension.php:255)
  at Bolt\Twig\FieldExtension->selectOptionsContentType(object(SelectField))
     (vendor/bolt/core/src/Twig/FieldExtension.php:213)
  at Bolt\Twig\FieldExtension->selectOptions(object(SelectField))
     (var/cache/dev/twig/35/354d023db4d40905d60ed64367dda109f3741095dcecb06c66f49c16938b7c5e.php:50)
  at __TwigTemplate_3fdcff874b050495e998b65d907cdc8f9af6d1d08c8e6fbcbdbfcc5e1a9dae4c->doDisplay(array('compound_label' => 'Woorden', 'id' => 'field-popups-woorden-1-weergave', 'field' => object(SelectField), 'name' => 'collections[popups][woorden][1][weergave]', 'record' => object(Content), 'include_id' => true, 'app' => object(AppVariable), 'config' => object(Config), 'defaultLocale' => 'en'), array('field' => array(object(__TwigTemplate_3fdcff874b050495e998b65d907cdc8f9af6d1d08c8e6fbcbdbfcc5e1a9dae4c), 'block_field')))
     (vendor/twig/twig/src/Template.php:394)
  at Twig\Template->displayWithErrorHandling(array('compound_label' => 'Woorden', 'id' => 'field-popups-woorden-1-weergave', 'field' => object(SelectField), 'name' => 'collections[popups][woorden][1][weergave]', 'record' => object(Content), 'include_id' => true, 'app' => object(AppVariable), 'config' => object(Config), 'defaultLocale' => 'en'), array('field' => array(object(__TwigTemplate_3fdcff874b050495e998b65d907cdc8f9af6d1d08c8e6fbcbdbfcc5e1a9dae4c), 'block_field')))
     (vendor/twig/twig/src/Template.php:367)
  at Twig\Template->display(array('compound_label' => 'Woorden', 'id' => 'field-popups-woorden-1-weergave', 'field' => object(SelectField), 'name' => 'collections[popups][woorden][1][weergave]', 'record' => object(Content), 'include_id' => true), array())
     (vendor/twig/twig/src/TemplateWrapper.php:47)
    ...

This error was really hard to diagnose, but in the end it boiled down to an issue caused by the order of initialization of the fields. Somehow I did end up with the select field having a higher id than that of the set it is in, but the set having lower id than the collection it is part of. This causes issues in the case of our select field, because the logic for combining content (from db) with configuration (from contenttypes.yml) needs a full list of parents (of parents of parents...) but our id combination combined with the initialization order of Doctrine results in one parent missing, with results is no 'values' found for the select, which results in some part of FieldExtension.php 'thinking' it must be a select that uses other content types, and that function finally breaking horribly because the 'values' is in fact 'null'.

I think that even if in general the order of the ids is preventing this, it should not be programmed in a way that is dependent on the id order. I might have a fix, but that one probably should be checked thoroughly.

(I'll expand this later and/or submit a PR)

Details

| Question | Answer |------------------------------------------------------ | ------ | Relevant Bolt Version | 5.1.2 | Install type | Composer install

Translations from the symfony translation panel don't map to the record. You can hit the edit button, change the value and even pressing the save and sync button show nothing unusual, except the submitted value doesn't map to the record. Changes are saved in the panel, which are visible if you attempt to edit the fields again, but they either don't submit properly or they are not retrieved properly.

This button doesnt do anything. It shows a loading icons for a couple of seconds and a message "Started synchronization of all translations", except nothing happens. Could also be stuck in a loop.

Fallback always shows 0.

Neither the sync buttons, nor the add selected messages seems to do the trick. They show the same loading animation and also nothing further seems to happen.

This is what you see when you press the edit button.

I took the effort to browse through all languages of the localeswitcher on the frontend to make sure it wasn't accidentally mapped to the wrong language for whatever reason.

This is my boltforms field config for the record.

        fields:
            company:
                type: text
                options:
                    required: true
                    label: companyname
                    constraints: [ NotBlank, { Length: { 'min': 2, 'max': 128 } } ]
            name:
                type: text
                options:
                    required: true
                    label: name
                    constraints: [ NotBlank, { Length: { 'min': 2, 'max': 128 } } ]
            phonenumber:
                type: text
                options:
                    required: true
                    label: phonenumber
                    constraints: [ NotBlank, { Length: { 'min': 2, 'max': 128 } } ]
            email:
                type: email
                options:
                    required: true
                    label: email
                    constraints: [ Email ]
                    help: "test"
            message:
                type: textarea
                options:
                    required: true
                    label: message
                    attr: 
                        rows: 6
            contactpreference:
                type: choice
                options:
                    label: contactpreference
                    choices:
                        email: email
                        phonecall: phonecall
                    multiple: false
                    expanded: true
            submit:
                type: submit
                options:
                    label: submit
                    attr:
                         class: 'form-button'

This shows my services.yaml setup. no other values have been changed:

parameters:
    locale: 'nl'
    # This parameter defines the codes of the locales (languages) enabled in the application
    app_locales: nl|en|fr|cz|sk
    app.notifications.email_sender: [email protected]
    bolt.table_prefix: bolt_
    bolt.backend_url: /bolt


services:
    # default configuration for services in *this* file
    _defaults:
        autowire: true      # Automatically injects dependencies in your services.
        autoconfigure: true # Automatically registers your services as commands, event subscribers, etc.
        public: false       # Allows optimizing the container by removing unused services; this also means
                            # fetching services directly from the container via $container->get() won't work.
                            # The best practice is to be explicit about your dependencies anyway.
        bind:               # defines the scalar arguments once and apply them to any service defined/created in this file
            $locales: '%app_locales%'
            $defaultLocale: '%locale%'
            $emailSender: '%app.notific'

This shows my contentypes config for the record:

pages:
    name: Pages
    singular_name: Page
    fields:
        title:
            type: text
            localize: true
            class: large
            group: content
        teaser:
            type: textarea
            localize: true
            postfix: |
                A text-only version of the content, that can be used to "tease"
                the content when it's used in listing pages or search results.
        image:
            type: image
            localize: true
            label: Highlighted image
        body:
            type: redactor
            localize: true
            height: 300px
        slug:
            type: slug
            localize: true
            uses: title
            group: Meta
        laik:
            type: text
            group: Meta
        template:
            type: templateselect
            filter: '/^(?!partials)[^_].*\.twig$/'
    locales: ['nl', 'en', 'fr']
    records_per_page: 5
    order: id

Details

| Question | Answer |----------------- | ------ | Relevant Bolt Version | 5.0.0 | Install type | composer install bolt:setup | BC Break | no | PHP version | 7.3.28 | Web server | Apache | For UX/UI issues | Brave, chromium, windows10

Bug summary

Translated labels don't save properly. The record cannot show the changes. The profiler translation backend shows the edited fields while still unrefreshed. It shows the edited value if you hit edit again. This either means they don't write properly to their locations or they are not retrieved properly.

Specifics

Any yourdomain.TLD/_profiler/ID?panel=translation should show the same behavior. the translations folder is currently only holding a .gitignore file it fails to produce the xml type files which would normally store the values.

Expected result

• values saved, stored and visible on page

Actual result

• loading and then no effect.

I'm playing with the new 5.0.0 beta 5 version of Bolt and I have a problem with checkbox fields in templates. I'm trying to fetch content where a checkbox field is checked, like this.

{% setcontent fooRecords = 'foos' where { checkboxField: true } %}

But I'm getting an exception:

Argument 2 passed to Bolt\Doctrine\JsonHelper::wrapJsonFunction() must be of the type string or null, bool given, called in /srv/www/vendor/bolt/core/src/Storage/SelectQuery.php on line 325

Details

| Question | Answer |----------------- | ------ | Relevant Bolt Version | 5.0.0 beta 5 | Install type | Composer install | BC Break | no | PHP version | 7.4.16 | Web server | nginx/1.19.3 | Database server | MySQL 5.7.32 | For UX/UI issues | -

Steps to reproduce

Contenttype like this:

foos:
    name: Foos
    singular_name: Foo
    fields:
        name:
            type: text
            variant: inline
            label: Name
        checkboxField:
            type: checkbox

Fetch contents like this:

{% setcontent fooRecords = 'foos' where { checkboxField: true } %}

Expected result

Contents according to where clause.

Actual result

Exception:

Argument 2 passed to Bolt\Doctrine\JsonHelper::wrapJsonFunction() must be of the type string or null, bool given, called in /srv/www/vendor/bolt/core/src/Storage/SelectQuery.php on line 325

TypeError:
Argument 2 passed to Bolt\Doctrine\JsonHelper::wrapJsonFunction() must be of the type string or null, bool given, called in /srv/www/vendor/bolt/core/src/Storage/SelectQuery.php on line 325

  at vendor/bolt/core/src/Doctrine/JsonHelper.php:23
  at Bolt\Doctrine\JsonHelper::wrapJsonFunction()
     (vendor/bolt/core/src/Storage/SelectQuery.php:325)
  at Bolt\Storage\SelectQuery->build()
     (vendor/bolt/core/src/Storage/Handler/SelectQueryHandler.php:44)
  at Bolt\Storage\Handler\SelectQueryHandler->__invoke()
  at call_user_func()
     (vendor/bolt/core/src/Storage/ContentQueryParser.php:457)
  at Bolt\Storage\ContentQueryParser->fetch()
     (vendor/bolt/core/src/Storage/Query.php:66)
  at Bolt\Storage\Query->getContentByScope()
     (vendor/bolt/core/src/Storage/Query.php:86)
  at Bolt\Storage\Query->getContentForTwig()
     (var/cache/dev/twig/a9/a99dd26a4bb9ce7a3019e8513c7c3ecdee55e2f6566eb0648e2629c5705d3b59.php:139)
  at __TwigTemplate_5910ccc0b8688d80c6c414080f4399caf6f7d50e1695877bd8ad7f7844cb8b49->block_main()
     (vendor/twig/twig/src/Template.php:171)
  at Twig\Template->displayBlock()
     (var/cache/dev/twig/5b/5b57a53ec61eb780bb228fd541f88b33d57086bbd6b7ffc27bd025ad55d7cefc.php:219)
  at __TwigTemplate_1f1c69ee45af87ebc36a5194ed5e08d7fda52bd54b27c398dee8f2ae51e2af37->doDisplay()
     (vendor/twig/twig/src/Template.php:394)
  at Twig\Template->displayWithErrorHandling()
     (vendor/twig/twig/src/Template.php:367)
  at Twig\Template->display()
     (var/cache/dev/twig/a9/a99dd26a4bb9ce7a3019e8513c7c3ecdee55e2f6566eb0648e2629c5705d3b59.php:48)
  at __TwigTemplate_5910ccc0b8688d80c6c414080f4399caf6f7d50e1695877bd8ad7f7844cb8b49->doDisplay()
     (vendor/twig/twig/src/Template.php:394)
  at Twig\Template->displayWithErrorHandling()
     (vendor/twig/twig/src/Template.php:367)
  at Twig\Template->display()
     (var/cache/dev/twig/0a/0afa37713518f5bc9d0e4a86d9b75c7160c4a49ab13d5fc31aa10b3414c5a9dc.php:47)
  at __TwigTemplate_fcb02321d9a6f1382205ebbac478d1f563d3d0d533c9bf31c4cc325fad0fb623->doDisplay()
     (vendor/twig/twig/src/Template.php:394)
  at Twig\Template->displayWithErrorHandling()
     (vendor/twig/twig/src/Template.php:367)
  at Twig\Template->display()
     (vendor/twig/twig/src/Template.php:379)
  at Twig\Template->render()
     (vendor/twig/twig/src/TemplateWrapper.php:40)
  at Twig\TemplateWrapper->render()
     (vendor/twig/twig/src/Environment.php:277)
  at Twig\Environment->render()
     (vendor/bolt/core/src/Controller/TwigAwareController.php:108)
  at Bolt\Controller\TwigAwareController->render()
     (vendor/bolt/core/src/Controller/TwigAwareController.php:158)
  at Bolt\Controller\TwigAwareController->renderSingle()
     (vendor/bolt/core/src/Controller/Frontend/HomepageController.php:56)
  at Bolt\Controller\Frontend\HomepageController->homepage()
     (vendor/symfony/http-kernel/HttpKernel.php:157)
  at Symfony\Component\HttpKernel\HttpKernel->handleRaw()
     (vendor/symfony/http-kernel/HttpKernel.php:79)
  at Symfony\Component\HttpKernel\HttpKernel->handle()
     (vendor/symfony/http-kernel/Kernel.php:195)
  at Symfony\Component\HttpKernel\Kernel->handle()
     (public/index.php:30)            

At the moment there is no way to do server-side validation of content entered via the bolt editor. (There is a little bit of validation done via javascript in the browser.)

I'm proposing to make a minimal set of changes that will allow developers who are using bolt/core to build a site to specify their own validation in php. These changes also make it possible for bolt/core to include server side validation itself later, while allowing developers to override this.

How can you help?

I'll be happy to discuss the options, and can provide an outline of the changes as I would see them.

I've started on a proof-of-concept, and can create a proposal for the change as a PR in the short future (days/weeks).

Outline of changes

I think this would work:

The basic approach would be to use as much code and knowledge from symfony/validator as possible, but to not force the use of it.

Create a new interface definition: ContentValidatorInterface, that has a single function: validate() - this function takes a content object, and returns an array-like structure of constraint violations. ConstraintViolationListInterface (used by symfony/validator) should definitely be allowed as a return value. The structure of the items in the array should follow the structure als used by symfony/validator.

Add code to the save() function in ContentEditController.php that will invoke the validate function if ContentValidatorInterface is available/injected. It should show the edit screen if the returned array has elements (instead of saving the data), and pass an additional 'errors' twig variable containing the violations.

Change twig templates: templates/content/edit.html.twig, and probably templates/_partials/fields/_base.html.twig templates to show the errors in the edit page.

With the above 3 changes a developer could create a validator class that implements ContentValidatorInterface as a service, and create as much validation as they want. Note that this is server-side only, implementing client-side validation that will match this should be left for another day.

PHP is outputting deprecation notices when run via the CLI.

PHP Deprecated:  Optional parameter $qb declared before required parameter 
$utils is implicitly treated as a required parameter in 
vendor/bolt/core/src/Storage/SelectQuery.php on line 111

Details

| Question | Answer |------------------------------------------------------ | ------ | Relevant Bolt Version | 5.0.7 | Install type | Composer | BC Break | no | PHP version | 8.1

Reproduction

Upgrading to PHP 8.1 and my app's cronjobs start throwing the above error.

Fixes #1971 - the CAST to TEXT causes an error on MySQL.

This follows similar logic implemented in src/Doctrine/Query/Cast.php.

Getting the backend driver name (e.g. mysql) is a long chain of method calls but I cannot see any other way. It also uses getDatabasePlatform()->getName() instead of the getDriver()->getName() call in Cast.php as the docblock on that method suggests it is deprecated (but no alternative suggested.)

In Bolt 3, if you do {{ record.fieldname }}, it'll output HTML. At the same time, it's not explicitly defined how it should behave. One of the causes of this is how the fields are stored internally.

We should make sure that Bolt 4 does this sensibly, consistent and robust. In my opinion, it should work like the following. Let's say we have a title field, with a <i> tag in it.

In Twig we should be able to do:

<hr>
    <p>{{ record.title }}</p>
    <p>{{ record.title|raw }}</p>
    <p>{{ record.title|e('html') }}</p>
    <p>{{ dump(record.title) }}</p>
    <p>{{ dump(record.title.getValue()) }}</p>
<hr>

And it should output:

This way, the implementor can use {{ record.foo }} and get the HTML output they expect 90% of the time, and at the same time, you still have access to the underlying data structure to do with it what you need.

Details

| Question | Answer |------------------------- | ------ | Relevant Bolt Version | 4.1.4 | Install type | Composer install | BC Break | no | PHP version | 8.0 RC3 | Web server | Nginx | For UX/UI issues | Latest Chrome

Reproduction

Bug summary

BoltCMS currently breaks when trying to run it on PHP 8.0 RC3

Specifics

After installing the current PHP 8.0 RC3 release I got the following error when trying to access the frontpage

Compile Error: Cannot declare interface Psr\Container\ContainerInterface, because the name is already in use

This is related to https://github.com/symfony/symfony/issues/36676

Basically you can either have the psr/container interface installed via composer or as a PHP module.

To circumvent that we need to add the following to the composer.json

{
    "replace": {
        "psr/container": "1.*"
    }
}

After a new composer install the following error occurs

syntax error, unexpected token "match"

This is realted to https://github.com/willdurand/Negotiation/pull/106

The module https://github.com/willdurand/Negotiation is being required by api-platform/core which is present in our composer.json

But as can be seen in that Pull Request there is no stable release for that fix at the moment.

I tried that fix on my instance and BoltCMS works after these changes.

I would say we'll have to wait for a stable release and then adjust our TravisCI tests to check if other things break as well under 8.0

Bumps json5 to 2.2.2 and updates ancestor dependencies json5, @vue/cli-service, @symfony/webpack-encore, vue-jest and vue-loader. These dependencies need to be updated together.

Updates json5 from 2.2.1 to 2.2.2

Updates @vue/cli-service from 4.5.19 to 5.0.8

Updates @symfony/webpack-encore from 1.8.2 to 4.2.0

Updates vue-jest from 3.0.7 to 4.0.1

Updates vue-loader from 15.10.1 to 17.0.1

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

This feature adds the Content-Translation page:

This page allows to export content in the xlf format, which is the default format for translation agencies.

After translating the files, they can be imported again and will replace localized text with the given file.

If content cannot be found by their id (which happens if content is changed between import and exporting), the controller searches for the original text and adds the translation to the found content field.

This also works with custom fields that are stored as json. On export the controller even splits json content, so translation agencies do not need to read in between the json overhead:

    <unit id="fZD0nJb" name="DE TITLE">
      <notes>
        <note category="id">9</note>
        <note category="type">generic</note>
        <note category="original">{"title":"DE TITLE","size":"h2"}</note>
        <note category="part">title</note>
      </notes>
      <segment>
        <source>DE TITLE</source>
        <target>EN TITLE</target>
      </segment>
    </unit>
    <unit id="_Zj_Bq_" name="h2">
      <notes>
        <note category="id">9</note>
        <note category="type">generic</note>
        <note category="original">{"title":"DE TITLE","size":"h2"}</note>
        <note category="part">size</note>
      </notes>
      <segment>
        <source>h2</source>
        <target>h2</target>
      </segment>
    </unit>

HTML on the other side is not extracted, which was not a problem for the company that translated our last project (their tool was able to do it on its own).

This was tested on one project so far (without the fallback to the content query, if id's changed). This has also been successfully tested on all supported databases: mysql, sqlite and postgresql.

After installing Bolt CMS, i create my homepage page in backend.

Even i try to access by my local domain only or with the slug of the page, my browser can't present the page. I'm working with Nginx. When i examine the error log, i don't see any sensitive informations to explain it. But in the access log, each access return HTTP 302 code.

After I'm created a new page (Page ContentType). With my local domain and the slug of the new page, i can see it. This problem isn't depending of the graphic theme used.

Details

| Question | Answer |------------------------------------------------------ | ------ | Relevant Bolt Version | 5.1.19 | Install type | Composer install | BC Break | yes/no | PHP version | 8.1 | | Web server | Nginx | | For UX/UI issues | firefox (linux) 108.0 (64bits)

Reproduction

Install Bolt CMS with composer (create new project) execute setup after set database in .env.local (MariaDB) access to backend create the home page (with or without images) try to access at the root of the website

Bug summary

Specifics

Steps to reproduce

Install Bolt CMS with composer (create new project) execute setup after set database in .env.local (MariaDB) access to backend create the home page (with or without images) try to access at the root of the website

Expected result

Actual result

My browser show nothing an notify me an loading error

New content is saved to the database twice

error bolt.js:1:100516

bolt.js:1:98689 Uncaught ReferenceError: can't access lexical declaration 'l' before initialization t http://www.localhost:8000/assets/bolt.js:1 error http://www.localhost:8000/assets/bolt.js:1 u http://www.localhost:8000/assets/469.js:2 fireWith http://www.localhost:8000/assets/469.js:2 C http://www.localhost:8000/assets/469.js:2 t http://www.localhost:8000/assets/469.js:2 send http://www.localhost:8000/assets/469.js:2 ajax http://www.localhost:8000/assets/469.js:2 30720 http://www.localhost:8000/assets/bolt.js:1 dispatch http://www.localhost:8000/assets/469.js:2 handle http://www.localhost:8000/assets/469.js:2 add http://www.localhost:8000/assets/469.js:2 Ee http://www.localhost:8000/assets/469.js:2 each http://www.localhost:8000/assets/469.js:2 each http://www.localhost:8000/assets/469.js:2 Ee http://www.localhost:8000/assets/469.js:2 on http://www.localhost:8000/assets/469.js:2 t http://www.localhost:8000/assets/469.js:2 30720 http://www.localhost:8000/assets/bolt.js:1 l http://www.localhost:8000/assets/469.js:2 c http://www.localhost:8000/assets/469.js:2 setTimeout handler*19755/</Deferred/then/a/< http://www.localhost:8000/assets/469.js:2 u http://www.localhost:8000/assets/469.js:2 fireWith http://www.localhost:8000/assets/469.js:2 fire http://www.localhost:8000/assets/469.js:2 u http://www.localhost:8000/assets/469.js:2 fireWith http://www.localhost:8000/assets/469.js:2 ready http://www.localhost:8000/assets/469.js:2 W http://www.localhost:8000/assets/469.js:2 19755 http://www.localhost:8000/assets/469.js:2 19755 http://www.localhost:8000/assets/469.js:2 19755 http://www.localhost:8000/assets/469.js:2 s http://www.localhost:8000/assets/bolt.js:1 32025 http://www.localhost:8000/assets/469.js:2 s http://www.localhost:8000/assets/bolt.js:1 30720 http://www.localhost:8000/assets/bolt.js:1 s http://www.localhost:8000/assets/bolt.js:1 i http://www.localhost:8000/assets/bolt.js:1 O http://www.localhost:8000/assets/bolt.js:1 http://www.localhost:8000/assets/bolt.js:1 http://www.localhost:8000/assets/bolt.js:1

When attempting to delete a record using the REST API, a status "204 No Content" is returned (which indicates that the request was successful) but the record still remains unchanged.

Details

| Question | Answer |----------------- | ------ | Relevant Bolt Version | 5.1.18 | Install type | Composer install | PHP version | 7.2 | Web server | Apache / Built-in

Reproduction

Bug summary

* Most likely an APIPlatform implementation fault
* Annotations for deleting content using the API are present in Bolt\Entity\Content

Specifics

* API route is `/api/contents/{id}`, method is DELETE
* API definition can be found by default under `/bolt/api`
* Bolt was installed using Composer CLI
* Bolt version is 5.1.28
* Clients used to verify the problems are Postman and PHP/Curl

Steps to reproduce

* Create a User with ROLE_WEBSERVICE
* Create an example record of any content type
* Make an HTTP call with DELETE method to `/api/contents/{id}` -> should return status 204
* Verify that the record has not been deleted

Expected result

* The record is deleted from the database completely

Actual result

* The record remains unchanged