frojd / frojd-bedrock Goto Github PK

Included with logo, main menu, service menu and mobile menu

User setting is not working under Linux.

Change:

    db:
        image: mysql:5
        ports:
            - "{{cookiecutter.docker_db_port}}:3306"
        volumes:
            - "./docker/files/db-dumps/:/docker-entrypoint-initdb.d/"
            - "./db/:/var/lib/mysql"
        env_file: "./docker/config/db.env"
        user: "1000:50"

To:

    db:
        image: mysql:5
        ports:
            - "{{cookiecutter.docker_db_port}}:3306"
        volumes:
            - "./docker/files/db-dumps/:/docker-entrypoint-initdb.d/"
            - "./db/:/var/lib/mysql"
        env_file: "./docker/config/db.env"

Add a 404 page with a title and description collected from the admin theme settings

Collect information from theme settings page:

• link list
• follow links
• contact

Collect from theme settings

These tools should be included in WYSIWYG:

• p,h2,h3,h4,h5,h6
• bold, italic, underline, strikethrough
• bullet and number list
• hr
• block quote
• alignright, aligncenter, alignleft, alignjustify
• link, unlink
• pastetext, removeformat, undo, redo, help
• Format for preamble

Also add styling of the above and for inserting embedded code

Axe DevTools flagged that "Document does not have a main landmark" when i was testing a site based on Frojd-Bedrock.

I think the solution would be to replace <div role="document"> with <main> or <div role="main"> but maybe this should be done together with a bigger accessibility review on the whole project?

Add a theme settings page in admin with basic fields:

• 404 - title and description
• Footer - Link list, follow links, contact
• Cookie popup - Text
• Browser support popup - Text

These commands fails with YIKES! It looks like you're running this as root.

- name: Flush permalinks
  shell: chdir="{{ ansistrano_release_path.stdout }}"
    wp rewrite flush

- name: Flush cache
  shell: chdir="{{ ansistrano_release_path.stdout }}"
    wp cache flush

in after-symlink.yml.

I suggest either to add --allow-root or the soulution below.

- name: Flush permalinks
  shell: chdir="{{ ansistrano_release_path.stdout }}"
    runuser -u www-data -- wp rewrite flush

- name: Flush cache
  shell: chdir="{{ ansistrano_release_path.stdout }}"
    runuser -u www-data -- wp cache flush

Add default .po and .mo-files for translation

Some problems occur when using the provision and then on deploy:

• Using user "deploy" on provision doesn't work since releases-directory can't be created in app directory
• Setting user "deploy" to uploads directory in after-setup makes the uploads directory not writable for uploading files from wordpress

Change so provision is done with root and then any changes to ownership can be added afterwards. Also make sure the user set to the uploads directory can write to directory from WP

In docker-compose.yml elasticsearch:2.4 is specified, but Elasticpress recomends 5.0+. Would it be ok to update to 5.6.10?

Had an issue where I could not see my changes after deploy. Resolved it by flushing nginx cache in wp admin. But i think it should be a part of the release flow.

Added this to after-symlink.yml in my project. Maybe it should go into the boilerplate?

- name: Purge Nginx Cache
  shell: /bin/rm -rf /var/lib/nginx/fastcgi_cache/*

The authors dropdown in page editing won't be visible since the endpoint for users is removed in security file in theme.

Fix this by adding early return in 'rest_endpoints'-filter for logged in users

Add a walker for wp_page_menu and wp_nav_menu with classes in bem-structure