Drupal 8.x

Practically each day my database grows to about half a GB in size. The only way I have found to solve this problem is by manually clearing the caches. After this the size returns to about 80 MB. Cron is run every three hours and "browser and proxy cache maximum age" are set to "no caching".

Is there anything I can do to automatically keep the database size down?

Hello friends,

I was wandering if anybody could offer some advice as to what might be going on. I have a Drupal installation with a custom module working fine on my local environment, but as soon as I upload it to my Hetzner manged server, I get the following error: 

Parse error: syntax error, unexpected ':', expecting ';' or '{' in /usr/www/users/platfkkuax/uconomy_demo/vendor/doctrine/annotations/lib/Doctrine/Common/Annotations/AnnotationRegistry.php on line 50

Added a custom View Block to display an image and title. Just wondering how'd go about styling the Title with CSS?

I have a Block Restricted to the Frontpage using (<front>. Expecting said block to only appear on the main index of my domain.com, the block also appears on pagination pages too eg: domain.com/?page=3

Have I set something up incorrectly?

When logged in as the Administrator, the URL on my site (as of 1 week) shows the index.php in the address:
eg: "https:mysite.com/index.php/features/2019_Oscars_revealed"

I had this issue about a year ago and resolved it with the help of my (shared server) hosting Co. by adding some code to the root .htaccess file.

This is described in:

Fix Drupal 8 'Clean URLs' problems
Last updated on 7 January 2019

I have a scenario where users need to create custom 'rooms', and then browse a furniture catalogue to add furniture items to a given room (kind of like a cart or wishlist, but they can create multiple lists). I'm doing this via entity references, so that a 'room' content type has an entity reference field that the user uses to add furniture items.

Is it possible to have a workflow where the user adds an item to a 'room' from the context of viewing a furniture item? The ideal workflow would be: