By Keirebu on

Hi!

I'm still learning Drupal, and, I need to update to the most recent version, sadly I have attempt to update my site twice, unsuccessfully....What is the best way to update Drupal? I can't afford to loose the data already on my site... What is the safest method, what do you suggest?

Thank you!

⋅ Categories: Drupal 8.x

Comments

VM’s picture

VM commented

https://www.drupal.org/docs/8/update/update-procedure-in-drupal-8

Keirebu’s picture

Keirebu commented

I'm familiar with the instructions, I'm following these and kill the site... That's why I'm asking for help, I'm missing something.

I have a host running Drupal, so I'm not sure if I can even use Composer or Drush. Can I? How do I run one of these options on a server that I don't maintain?

Jaypan’s picture

Jaypan commented

I'm familiar with the instructions, I'm following these and kill the site...

How can we help you beyond giving you the instructions?

Keirebu’s picture

Keirebu commented

If I knew what the problem was, I would have a starting point :(

No matter what I do I just keep shutting my site down. I'm not a coder, and I'm starting to think that Drupal could be a mistake. Honestly I'm not sure I understand the Composer or Drush options. The instructions seems easy, but how do I access the shell? How do I install these on a hosted server? Do I already have these installed? Which would be better to use, Composer or Drush?

See my problem? I'm lost and simply don't know where to start....

Jaypan’s picture

Jaypan commented

Well the first thing you need to do is figure out what the actual problem is. 'Shutting down' is not particularly descriptive. When the error occurs, you need to go into the error logs (Drupal, PHP and Apache) to find out what the actual error is.

Keirebu’s picture

Keirebu commented

I'm sorry it isn't descriptive, I tried several weeks ago, and I'm now just getting back to the Drupal project.

The error came from my lack up understanding on how to manually implement the upgrade. Which is why I want to attempt the upgrade with either Drush or Composer. But I'm not sure which I should use, if they are already installed on my site, and if they aren't how do I install them on a remote server?

Maybe that is a better start? I will keep the question small :)

Thank you!

mmjvb’s picture

mmjvb commented

It is not looking into the cause of the failure to update that is the problem. Trying alternatives is not going to help.
The manual way to update should always work. Suggest to listen to the advice and work on finding out the cause, instead of concentrating on alternatives that are beyond your comfort zone.

With the abstract description, kill the site, you made your point clear. Now, you need to provide specifics if you want us to help. You need to be explicit in what you did how, so we can tell you where you went wrong. When you didn't go wrong, you need to tell us what happened. Again, no abstract conclusions, but facts!

When you can't help yourself this way, anything to do with a computer will be a mistake!

Keirebu’s picture

Keirebu commented

I finally tried the update on a more reliable internet connection, and amazingly, it worked... all files transferred and the update was a success... BUT I have the following issues, could you please shed some light on these?

Errors found
Trusted Host Settings: Not enabled
The trusted_host_patterns setting is not configured in settings.php. This can lead to security vulnerabilities. It is highly recommended that you configure this. See Protecting against HTTP HOST Header attacks for more information.

I'm still reading about this issue... not sure I understand how to fix this, but I'm reading...

Warnings found
PHP OPcode caching: Not enabled
PHP OPcode caching can improve your site's performance considerably. It is highly recommended to have OPcache installed on your server.

Do I need to install OPcache, or does my host?

Jaypan’s picture

Jaypan commented

There is lots of information out there on your first issue. For your second issue, your host will need to install OPcache.

fkelly12054@gmail.com’s picture

fkelly12054@gmail.com commented

On a shared host system your host would need to install opcache. They probably won't. Opcache just speeds up your site but you can live just fine without it. Just ignore the warning for now.

Keirebu’s picture

Keirebu commented

Thank you :)

Keirebu’s picture

Keirebu commented

I have no desire to mess this up, so I'm just going to verify, to address this issue...

Errors found
Trusted Host Settings: Not enabled
The trusted_host_patterns setting is not configured in settings.php. This can lead to security vulnerabilities. It is highly recommended that you configure this. See Protecting against HTTP HOST Header attacks for more information.

If my domain was v8.keirebu.com I need to add the following to the bottom of settings.php correct?

*
*
*/

$settings['trusted_host_patterns'] = array(
'^v8.keirebu\.com$',
'^.+\.v8.keirebu\.com$',
);

/**
*

Keirebu’s picture

Keirebu commented

Well I just thought I would try it, what's the worse that could happen right? You learn from mistakes :)

Um.... after adding the following to the bottom of settings.php

*
*
*/

$settings['trusted_host_patterns'] = array(
'^v8.keirebu\.com$',
'^.+\.v8.keirebu\.com$',
);

/**
*

Or even:

*
*
*/

$settings['trusted_host_patterns'] = array(
'^keirebu\.com$',
'^.+\.keirebu\.com$',
);

/**
*

I got the following error both times:

Parse error: syntax error, unexpected '*' in /homepages/30/d673701508/htdocs/clickandbuilds/Drupal/keirebu/sites/default/settings.php on line 770

Keirebu’s picture

Keirebu commented

Problem solved... Thank you.

fkelly12054@gmail.com’s picture

fkelly12054@gmail.com commented

Not sure how you are editing your settings.php. If it's in cpanel, use the code editor, which will show you the line numbers. Or use an PHP editor on your PC that will show you the line numbers. Try Googling "PHP comment block". /** is the start of a comment block and */ is the end of one. If you just stick a * character on a line in PHP by itself and that * is not within a comment block, you will get an error ... as you can see. An editor with line numbers will show you exactly which line is in error.

Disregard reply. Was posting when you posted that the problem was solved. Still using an editor that shows line numbers is a good idea.