mautic / mautic/user-documentation

Documentation issues / clarification with update instructions

Open
#245 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mautic 5
Dominant language
Shell
Stars
22
Forks
76
Avg merge
22h 9m
Merged PRs (30d)
33

Description

I was following the instructions in this topic to update from mautic 5.0.2 to 5.0.3.

I'm using a composer based installation.

https://docs.mautic.org/en/5.x/getting_started/how_to_update_mautic.html

When running the commands under step 5 of Updating Mautic (composer based installs, I ran into the following issues:

  1. Running the second command bin/console mautic:update:apply --finish gives an error "You have composer updates enabled. This means that you can only update Mautic through the 'composer update' command." Should this line be removed then from the documentation?

  2. Running bin/console doctrine:schema:update --no-interaction --force I received errors:

    Updating database schema...
    
    In ExceptionConverter.php line 117:
    
    An exception occurred while executing a query: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'IDX_1AE3441319EB6921'; check that column/key exists
    
    In Exception.php line 28:
    
    SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'IDX_1AE3441319EB6921'; check that column/key exists
    
    In Connection.php line 33:
    
    SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'IDX_1AE3441319EB6921'; check that column/key exists
    

    I'm not sure if those are valid errors, or just because the migrations already applied them in the previous step. In most migration technologies I've used in the past you can make schema and data updates apply in one command. I'm sorry I'm not familiar with doctrine migrations.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Updating Mautic page, especially step 5 for composer-based installs, and reproduce the listed commands if the required environment is available. Verify the composer-update message and the doctrine:schema:update error, then update the instructions so the documented sequence and expected outcomes are clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.