Bienvenue, Invité
Nom d'utilisateur : Mot de passe :


This Help forum is for issues relates to the latest release (1.7.10/11/12). For issues related to development versions please use their own Help forum.
Before asking for help please read "How to request help" by clicking on that tab above here."
  • Page :
  • 1
  • 2

SUJET : [SOLVED] Could not upgrade since 1.7.9

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #21

  • ddrury
  • Portrait de ddrury
  • Hors Ligne
  • Senior
  • Messages : 260
Just before you do that insert the following
var_dump($memory_limit);
just after
$memory_limit = Site::getPreference('MEMORY_LIMIT');

and
var_dump($max_execution_time);
just after
$max_execution_time = Site::getPreference('MAX_EXECUTION_TIME');

Doh hit submit in error
--
Dave

Local: Win 10 Pro, Apache 2.4.17 virtual hosts, PHP 5.4.21, 5.5.15, 5.6.16 & 7.0.0, Mysql 5.7.9 all 64bit
Production: linux 2.6.32.21-grsec #5 SMP, Apache 2.2, PHP 5.6.15, Mysql 5.5.28-29.1
Dernière édition: il y a 3 mois 2 semaines par ddrury.
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #22

  • ddrury
  • Portrait de ddrury
  • Hors Ligne
  • Senior
  • Messages : 260
Just before you do that insert the following
var_dump($memory_limit);
just after
$memory_limit = Site::getPreference('MEMORY_LIMIT');

and
var_dump($max_execution_time);
just after
$max_execution_time = Site::getPreference('MAX_EXECUTION_TIME');

Both should give null as the result
--
Dave

Local: Win 10 Pro, Apache 2.4.17 virtual hosts, PHP 5.4.21, 5.5.15, 5.6.16 & 7.0.0, Mysql 5.7.9 all 64bit
Production: linux 2.6.32.21-grsec #5 SMP, Apache 2.2, PHP 5.6.15, Mysql 5.5.28-29.1
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #23

  • vbke
  • Portrait de vbke
  • Hors Ligne
  • New
  • Messages : 16
I get: string(4) "128M" string(3) "120"
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #24

  • vbke
  • Portrait de vbke
  • Hors Ligne
  • New
  • Messages : 16
or is that because those values are still in my preference setting?
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #25

  • ddrury
  • Portrait de ddrury
  • Hors Ligne
  • Senior
  • Messages : 260
Yes,

But if you actually delete the entries you should still see those values in grey (indicating suggested values). If they are already empty we'll need to delve further
--
Dave

Local: Win 10 Pro, Apache 2.4.17 virtual hosts, PHP 5.4.21, 5.5.15, 5.6.16 & 7.0.0, Mysql 5.7.9 all 64bit
Production: linux 2.6.32.21-grsec #5 SMP, Apache 2.2, PHP 5.6.15, Mysql 5.5.28-29.1
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #26

  • vbke
  • Portrait de vbke
  • Hors Ligne
  • New
  • Messages : 16
I deleted the values in the preferences.

Followed your instructions and I get:
string(0) "" string(0) ""
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #27

  • ddrury
  • Portrait de ddrury
  • Hors Ligne
  • Senior
  • Messages : 260
Well I can see why our values differ - If the values have never been set then you get null, if they've been set and deleted then you get the empty string

Does the site work once those values have been deleted? If so maybe your host has a limit on the values, try reducing them and see what happens, otherwise I'd copy the complete chunk of code from
if (!ini_get('safe_mode')) {} to your host and ask why this causes your site to fail

And just out of interest I can load your site fine at the moment!
--
Dave

Local: Win 10 Pro, Apache 2.4.17 virtual hosts, PHP 5.4.21, 5.5.15, 5.6.16 & 7.0.0, Mysql 5.7.9 all 64bit
Production: linux 2.6.32.21-grsec #5 SMP, Apache 2.2, PHP 5.6.15, Mysql 5.5.28-29.1
Dernière édition: il y a 3 mois 2 semaines par ddrury.
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #28

  • vbke
  • Portrait de vbke
  • Hors Ligne
  • New
  • Messages : 16
I removed those 2 var_dump lines and now webtrees works and keeps on working. I am a bit confused now. I gues that the max_memory & time settings in my site prefferences apparently were NOK. I Have no clue since I didn't touch that probably since the beginning I started with webtrees. Now that those values are cleared, it works ;-)
L'administrateur a désactivé l'accès en écriture pour le public.
Avez-vous besoin d'une solution d'hébergement web pour votre site webtrees ?
Si vous préférez un hébergeur spécialisé de webtrees, la page suivante en liste quelques-uns capables de vous offrir ce type de service :

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #29

  • vbke
  • Portrait de vbke
  • Hors Ligne
  • New
  • Messages : 16
many thanks!
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #30

  • ddrury
  • Portrait de ddrury
  • Hors Ligne
  • Senior
  • Messages : 260
You're very welcome.

Just noticed that near the beginning of this thread you mention that your support asked you to put two lines in index.php one of which was an ini_set line so clearly they do support that. So maybe they put a limit on the values you can use with memory limit and/or max execution time.

Who knows! anyway glad it's working.
--
Dave

Local: Win 10 Pro, Apache 2.4.17 virtual hosts, PHP 5.4.21, 5.5.15, 5.6.16 & 7.0.0, Mysql 5.7.9 all 64bit
Production: linux 2.6.32.21-grsec #5 SMP, Apache 2.2, PHP 5.6.15, Mysql 5.5.28-29.1
L'administrateur a désactivé l'accès en écriture pour le public.

Could not upgrade since 1.7.9 il y a 3 mois 2 semaines #31

  • fisharebest
  • Portrait de fisharebest
  • en ligne
  • Administrator
  • Messages : 11465
Many web hosts do mot allow you to request more resourses.

Akso, it is not possible to detect if we are allowed more resources.

In webtrees 2, these server changes are now part of a custom module. So, if your webhist changes their policy, you can revover your site by deleting yhe custom module.
Greg Roach - Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. - fisharebest.webtrees.net
L'administrateur a désactivé l'accès en écriture pour le public.
  • Page :
  • 1
  • 2
Propulsé par Kunena