New install, blank page with «Error»
Topic is solved
Moderator: General Support Moderators
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
New install, blank page with «Error»
So I’ve installed a fresh copy of Joomla! to my CentOS7 server. No DNS configured yet, so I try by IP:
http://107.152.32.67/
As expected, it redirects to ./installation/index.php, but then I get a blank page with the word «Error» on it.
I think it’s from a 404 error. But I used HowToForge to make sure I walked through the steps. I’m using a LAMP stack (so, Apache, and MariaDB, and PHP7.2.9). Prior to copying the latest version of Joomla!, I was able to get the phpinfo screen, and the default Apache screen.
When I try via wget http://localhost, I get:
Code: Select all
[***]# wget http://localhost
--2018-08-21 21:36:39-- http://localhost/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:80... failed: Connection refused.
Connecting to localhost (localhost)|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: installation/index.php [following]
--2018-08-21 21:36:39-- http://localhost/installation/index.php
Reusing existing connection to localhost:80.
HTTP request sent, awaiting response... 500 Internal Server Error
2018-08-21 21:36:39 ERROR 500: Internal Server Error.I’m not worried about the IPv6. I’ll deal with that later.
Thoughts?
-
Webdongle
- Joomla! Master
- Posts: 42391
- Joined: Sat Apr 05, 2008 9:58 pm
Re: New install, blank page with «Error»
Post
by Webdongle » Tue Aug 21, 2018 9:57 pm
Why the IP address not url?
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
Re: New install, blank page with «Error»
Post
by RobJVargas » Wed Aug 22, 2018 3:38 pm
Webdongle wrote: ↑
Tue Aug 21, 2018 9:57 pm
Why the IP address not url?
As I said, I haven’t configured DNS yet.
The HowToForge page says it’s not needed for that install connection. Digital Ocean’s page shows the same.
-
ThomasGHarris
- Joomla! Apprentice
- Posts: 14
- Joined: Thu Aug 02, 2018 5:02 am
Re: New install, blank page with «Error»
Post
by ThomasGHarris » Wed Aug 22, 2018 10:35 pm
Hi Rob,
Is there any other error log? Is this the full Joomla package? Seems more like the installation or the server are not accepting one another.
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
Re: New install, blank page with «Error»
Post
by RobJVargas » Fri Aug 24, 2018 10:03 pm
@ThomasGHarris: Here’s a tail output of error-log:
Code: Select all
[Fri Aug 24 21:44:01.893018 2018] [lbmethod_heartbeat:notice] [pid 6704] AH02282: No slotmem from mod_heartmonitor
[Fri Aug 24 21:44:01.916404 2018] [mpm_prefork:notice] [pid 6704] AH00163: Apache/2.4.6 (CentOS) PHP/7.2.9 configured -- resuming normal operations
[Fri Aug 24 21:44:01.916439 2018] [core:notice] [pid 6704] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Fri Aug 24 21:51:00.546639 2018] [mpm_prefork:notice] [pid 6704] AH00170: caught SIGWINCH, shutting down gracefully
[Fri Aug 24 21:51:01.681294 2018] [suexec:notice] [pid 6717] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Aug 24 21:51:01.720944 2018] [so:warn] [pid 6717] AH01574: module php7_module is already loaded, skipping
[Fri Aug 24 21:51:01.723250 2018] [auth_digest:notice] [pid 6717] AH01757: generating secret for digest authentication ...
[Fri Aug 24 21:51:01.724203 2018] [lbmethod_heartbeat:notice] [pid 6717] AH02282: No slotmem from mod_heartmonitor
[Fri Aug 24 21:51:01.748370 2018] [mpm_prefork:notice] [pid 6717] AH00163: Apache/2.4.6 (CentOS) PHP/7.2.9 configured -- resuming normal operations
[Fri Aug 24 21:51:01.748403 2018] [core:notice] [pid 6717] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'A tail -f doesn’t show anything more than this. I can’t see anything that clearly points out why the index.php fails to run.
@Furiousnow: From what I can tell, I meet the supported requirements. PHP 7.2.9, Apache 2.4.6, Mysql 5.5.60 (MariaDB, just to be specific). httpd and mysql(mariadb) are running.
-
ThomasGHarris
- Joomla! Apprentice
- Posts: 14
- Joined: Thu Aug 02, 2018 5:02 am
Re: New install, blank page with «Error»
Post
by ThomasGHarris » Wed Aug 29, 2018 5:16 am
Hi Rob,
Is everything properly configured on the CentOS server? If you add any custom index.php is the same error showing? If it is instead of the index.php, it means that the server can’t load it. This is caused either by some missing htaccess(might be due to DNS not being available yet) or some permissions not granted.
-
deleted user
Re: New install, blank page with «Error»
Post
by deleted user » Wed Aug 29, 2018 9:41 am
When i was trying to get something i was working on working once i tried to upgrade to php 7.2 as that’s the highest version the host offers and i thought may as well have the latest version, but i got the same error. I had to downgrade to php 7.1 and the error went away.
-
brian
- Joomla! Master
- Posts: 12629
- Joined: Fri Aug 12, 2005 7:19 am
- Location: Leeds, UK
- Contact:
Re: New install, blank page with «Error»
Post
by brian » Wed Aug 29, 2018 1:27 pm
@webdongle that would be a pretty amazing solution as the OP has not even managed to install joomla
@Rob As it is your own server I would start by making sure that the server is configured correctly. Create a phpinfo.php file in the root and see if that runs without error (https://www.pipeten.com/support/scripti … info-page/)
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
Re: New install, blank page with «Error»
Post
by RobJVargas » Fri Aug 31, 2018 1:48 pm
@brian:
Sorry for the delay. «Real life» and all that.
I had the default Apache index.html working before I started installing Joomla!, and phpinfo worked prior to that as well. I’m going to re-enable phpinfo and see if that still works.
Sadly, I didn’t make a backup of my /var/www/html before I decompressed the Joomla files into it.
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
Re: New install, blank page with «Error»
Post
by RobJVargas » Fri Aug 31, 2018 2:04 pm
By the way, I’ve been under the impression that there is a missing module. Either a php module or an Apache one. So far, however, I’ve compared it to my other Joomla install and haven’t yet found the difference.
-
RobJVargas
- Joomla! Apprentice
- Posts: 7
- Joined: Thu Jan 04, 2018 8:40 pm
Re: New install, blank page with «Error»
Post
by RobJVargas » Fri Aug 31, 2018 3:16 pm
I was right. I was missing a php module. Not sure which one, but another site called tecadmin recommended the following for installing a LAMP server:
Code: Select all
install php-mysql php-xml
php-soap php-xmlrpc php-mbstring php-json php-gd php-mcryptOne of those modules did it. When I ran that, I noticed:
Code: Select all
Package php-mysql is obsoleted by php-mysqlnd, trying to install php-mysqlnd-7.2.9-1.el7.remi.x86_64 instead
...
Package php-mcrypt is obsoleted by php-pecl-mcrypt, trying to install php-pecl-mcrypt-1.0.1-6.el7.remi.7.2.x86_64 instead
My money is on php-mysqlnd, which did install, although php-pecl-mcrypt installed also.
In any event, I have the install page up and running now. Thanks for the assistance, guys. 
-
jimjam
- Joomla! Apprentice
- Posts: 10
- Joined: Thu Apr 26, 2012 9:56 am
- Location: Vienna, Austria
Re: New install, blank page with «Error»
Post
by jimjam » Tue Jan 29, 2019 7:57 am
I had the same problem installing Joomla 3.9.2. Installing php-xml fixed it for me.
-
valema
- Joomla! Fledgling
- Posts: 1
- Joined: Mon Dec 09, 2019 9:59 am
Re: New install, blank page with «Error»
Post
by valema » Mon Dec 09, 2019 10:05 am
I had the same thing (using localhost), and needed only to run
sudo apt-get install php-xml
Return to “Installation Joomla! 3.x”
Jump to
- Joomla! Announcements
- ↳ Announcements
- ↳ Announcements Discussions
- Joomla! 4.x — Ask Support Questions Here
- ↳ General Questions/New to Joomla! 4.x
- ↳ Installation Joomla! 4.x
- ↳ Administration Joomla! 4.x
- ↳ Migrating and Upgrading to Joomla! 4.x
- ↳ Extensions for Joomla! 4.x
- ↳ Security in Joomla! 4.x
- ↳ Templates for Joomla! 4.x
- ↳ Search Engine Optimization (Joomla! SEO) in Joomla! 4.x
- ↳ Language — Joomla! 4.x
- ↳ Performance — Joomla! 4.x
- ↳ Joomla! 4.x Coding
- Joomla! 3.x — Ask Support Questions Here
- ↳ General Questions/New to Joomla! 3.x
- ↳ Installation Joomla! 3.x
- ↳ Joomla! 3.x on IIS webserver
- ↳ Administration Joomla! 3.x
- ↳ Access Control List (ACL) in Joomla! 3.x
- ↳ Migrating and Upgrading to Joomla! 3.x
- ↳ Security in Joomla! 3.x
- ↳ Extensions for Joomla! 3.x
- ↳ Templates for Joomla! 3.x
- ↳ Search Engine Optimization (Joomla! SEO) in Joomla! 3.x
- ↳ Language — Joomla! 3.x
- ↳ Performance — Joomla! 3.x
- ↳ Joomla! 3.x Coding
- Joomla! Versions which are End of Life
- ↳ Joomla! 2.5 — End of Life 31 Dec 2014
- ↳ General Questions/New to Joomla! 2.5
- ↳ Installation Joomla! 2.5
- ↳ Joomla! 2.5 on IIS webserver
- ↳ Administration Joomla! 2.5
- ↳ Access Control List (ACL) in Joomla! 2.5
- ↳ Migrating and Upgrading to Joomla! 2.5
- ↳ Security in Joomla! 2.5
- ↳ Extensions for Joomla! 2.5
- ↳ Templates for Joomla! 2.5
- ↳ Search Engine Optimization (Joomla! SEO) in Joomla! 2.5
- ↳ Language — Joomla! 2.5
- ↳ Performance — Joomla! 2.5
- ↳ Joomla! 1.5 — End of Life Sep 2012
- ↳ General Questions/New to Joomla! 1.5
- ↳ Installation 1.5
- ↳ Joomla! 1.5 on IIS webserver
- ↳ Administration 1.5
- ↳ Migrating and Upgrading to Joomla! 1.5
- ↳ Security in Joomla! 1.5
- ↳ Extensions for Joomla! 1.5
- ↳ Templates for Joomla! 1.5
- ↳ Search Engine Optimization (Joomla! SEO) in Joomla! 1.5
- ↳ Language — Joomla! 1.5
- ↳ Performance — Joomla! 1.5
- ↳ Joomla! 1.0 — End of Life 22 July 2009
- ↳ Installation — 1.0.x
- ↳ Upgrading — 1.0.x
- ↳ Security — 1.0.x
- ↳ 3rd Party/Non Joomla! Security Issues
- ↳ Administration — 1.0.x
- ↳ Extensions — 1.0.x
- ↳ Components
- ↳ Modules
- ↳ Plugins/Mambots
- ↳ WYSIWYG Editors — 1.0.x
- ↳ Integration & Bridges — 1.0.x
- ↳ phpbb — Joomla! Integration
- ↳ Templates & CSS — 1.0.x
- ↳ Language — 1.0.x
- ↳ Joom!Fish and Multilingual Sites
- ↳ Performance — 1.0.x
- ↳ General Questions — 1.0.x
- Joomla! International Language Support
- ↳ International Zone
- ↳ Arabic Forum
- ↳ تنبيهات هامة
- ↳ الدروس
- ↳ 4.x جوملا!
- ↳ جوملا! 1.6/1.7
- ↳ الأسئلة الشائعة
- ↳ التثبيت و الترقية
- ↳ الحماية — و تحسين السرعة والأداء
- ↳ لوحة التحكم
- ↳ الإضافات البرمجية
- ↳ تعريب جوملا! و الإضافات البرمجية
- ↳ القوالب و التصميم
- ↳ صداقة محركات البحث
- ↳ القسم العام
- ↳ 1.5 !جوملا
- ↳ الأسئلة الشائعة
- ↳ التثبيت و الترقية
- ↳ الحماية — و تحسين السرعة والأداء
- ↳ لوحة التحكم
- ↳ الإضافات البرمجية
- ↳ تعريب جوملا! و الإضافات البرمجية
- ↳ القوالب و التصميم
- ↳ صداقة محركات البحث
- ↳ القسم العام
- ↳ جوملا! 1.0
- ↳ الأسئلة الشائـعة
- ↳ التثبيت
- ↳ لوحة التحكم
- ↳ الإضافات البرمجية
- ↳ الإضافات المعرّبة
- ↳ القوالب و التصميم
- ↳ الحماية — تحسين السرعة والأداء — صداقة محركات البحث
- ↳ القسم العام
- ↳ القسم العام
- ↳ !عرض موقعك بجوملا
- ↳ الأرشيف
- ↳ Bengali Forum
- ↳ Bosnian Forum
- ↳ Joomla! 1.5
- ↳ Instalacija i prvi koraci
- ↳ Ekstenzije
- ↳ Templejti
- ↳ Moduli
- ↳ Prevodi i dokumentacija
- ↳ Joomla! 1.7 / Joomla! 1.6
- ↳ Catalan Forum
- ↳ Notícies
- ↳ Temes sobre l’administració
- ↳ Temes sobre la traducció
- ↳ Components, mòduls i joombots
- ↳ Temes de disseny
- ↳ Webs realitzades amb Joomla!
- ↳ Offtopics
- ↳ Chinese Forum
- ↳ Croatian Forum
- ↳ Danish Forum
- ↳ Meddelelser
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x (Anbefalet til nye installationer. Nyeste funktionalitet)
- ↳ Installation, backup, opdatering og flytning — Godt igang
- ↳ Administration — Generel brug
- ↳ Komponenter, Moduler og Plugins
- ↳ Template, CSS og Design
- ↳ Nethandel, betaling m.m.
- ↳ Ældre versioner (disse vedligeholdes ikke længere fra officiel side)
- ↳ Joomla! 2.5 (Supporteres indtil 31. dec. 2014)
- ↳ Installation, backup, opdatering og flytning — Godt igang
- ↳ Administration — Generel brug
- ↳ Komponenter, Moduler og Plugins
- ↳ Template, CSS og Design
- ↳ Nethandel, betaling m.m.
- ↳ Joomla 1.5 (Tidligere langtidssupporteret version indtil sep. 2012)
- ↳ Installation, backup, opdatering og flytning — Godt igang
- ↳ Administration — Generel brug
- ↳ Komponenter, Moduler og Plugins
- ↳ Template, CSS og Design
- ↳ Nethandel, betaling m.m.
- ↳ Joomla 1.0 (Udgået version, der blev afløst af 1.5 i 2008)
- ↳ Installation, backup, opdatering og flytning — Godt igang
- ↳ Administration — Generel brug
- ↳ Komponenter, Moduler og Mambots
- ↳ Template, CSS og Design
- ↳ Nethandel, betaling m.m.
- ↳ Oversættelser (lokalisering)
- ↳ Joomla brugergrupper i Danmark
- ↳ JUG Kolding
- ↳ JUG København
- ↳ JUG Odense
- ↳ JUG Århus
- ↳ JUG Sorø
- ↳ Kommerciel (betalt) hjælp ønskes
- ↳ SEO
- ↳ FAQ — Dokumentation og vejledninger
- ↳ Vis dit websted
- ↳ Afviste ‘Vis dit websted’ indlæg
- ↳ Diverse (Off topic)
- ↳ Dutch Forum
- ↳ Aankondigingen
- ↳ Algemene vragen
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Installatie 3.x
- ↳ Extensies 3.x
- ↳ Templates 3.x
- ↳ Joomla! 2.5
- ↳ Installatie 2.5
- ↳ Componenten 2.5
- ↳ Modules 2.5
- ↳ Plugins 2.5
- ↳ Templates 2.5
- ↳ Joomla! 1.5
- ↳ Installatie
- ↳ Componenten
- ↳ Modules
- ↳ Plugins
- ↳ Templates
- ↳ Joomla! 1.0
- ↳ Installatie 1.0.x
- ↳ Componenten 1.0.x
- ↳ Modules 1.0.x
- ↳ Mambots 1.0.x
- ↳ Templates 1.0.x
- ↳ Vertalingen
- ↳ Offtopic
- ↳ Show jouw website
- ↳ Filipino Forum
- ↳ International Support Center
- ↳ Pinoy General Discussion & Archives
- ↳ Site Showcase
- ↳ Events
- ↳ Design Tips and Tricks
- ↳ Tsismis Zone
- ↳ Pinoy Translation Zone
- ↳ Pinoy Forum Archives
- ↳ Joomla! Philippines Local Forum www.joomla.org.ph
- ↳ Finnish Forum
- ↳ French Forum
- ↳ Les annonces!
- ↳ Le bistrot!
- ↳ L’expo!
- ↳ J! 4.x — L’atelier!
- ↳ J! 3.x — L’atelier!
- ↳ 3.x — Questions générales, nouvel utilisateur
- ↳ 3.x — Installation, migration et mise à jour
- ↳ 3.x — Sécurité et performances
- ↳ 3.x — Extensions tierce partie
- ↳ 3.x — Templates et design
- ↳ 3.x — Développement
- ↳ 3.x — Ressources
- ↳ J! 2.5.x — L’atelier!
- ↳ 2.5 — Questions générales
- ↳ 2.5 — Installation, migration et mise à jour
- ↳ 2.5 — Sécurité et performances
- ↳ 2.5 — Extensions tierce partie
- ↳ 2.5 — Templates et design
- ↳ 2.5 — Développement
- ↳ 2.5 — Ressources
- ↳ J! 1.5.x — L’atelier!
- ↳ 1.5 — Questions générales
- ↳ 1.5 — Installation, migration et mise à jour
- ↳ 1.5 — Sécurité et performances
- ↳ 1.5 — Extensions tierce partie
- ↳ 1.5 — Templates et design
- ↳ 1.5 — Développement
- ↳ 1.5 — Ressources
- ↳ J! 1.0.x — L’atelier!
- ↳ 1.0 — Questions générales
- ↳ 1.0 — Installation et mise à jour
- ↳ 1.0 — Sécurité
- ↳ 1.0 — Extensions tierce partie
- ↳ 1.0 — Templates et design
- ↳ 1.0 — Développement
- ↳ 1.0 — Ressources
- ↳ Besoin d’un professionel ?
- ↳ Extensions Open Source pour Joomla!
- ↳ German Forum
- ↳ Ankündigungen
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Allgemeine Fragen
- ↳ Installation und erste Schritte
- ↳ Komponenten, Module, Plugins
- ↳ Template, CSS und Designfragen
- ↳ Entwicklerforum
- ↳ Zeige Deine Webseite
- ↳ Joomla! 2.5
- ↳ Allgemeine Fragen
- ↳ Installation und erste Schritte
- ↳ Komponenten, Module, Plugins
- ↳ Template, CSS und Designfragen
- ↳ Entwicklerforum
- ↳ Zeige Deine Webseite
- ↳ Joomla! 1.5
- ↳ Allgemeine Fragen
- ↳ Installation und erste Schritte
- ↳ Komponenten, Module, Plugins
- ↳ Template, CSS und Designfragen
- ↳ Entwicklerforum
- ↳ Zeige Deine Webseite
- ↳ Professioneller Service
- ↳ Sonstiges (Offtopic)
- ↳ Archiv
- ↳ Joomla! 1.0
- ↳ Allgemeine Fragen 1.0.x
- ↳ Installation und erste Schritte 1.0.x
- ↳ Komponenten, Module, Mambots 1.0.x
- ↳ Template, CSS und Designfragen 1.0.x
- ↳ Entwicklerforum 1.0.x
- ↳ Zeige Deine Webseite 1.0.x
- ↳ Greek Forum
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Joomla! 2.5.x
- ↳ Joomla! 1.5.x
- ↳ Joomla! 1.0.x
- ↳ Hebrew Forum
- ↳ Indic Languages Forum
- ↳ Indonesian Forum
- ↳ FAQ
- ↳ Bantuan
- ↳ Komponen
- ↳ Modul
- ↳ Template
- ↳ Diskusi
- ↳ Italian Forum
- ↳ Guide
- ↳ Traduzioni
- ↳ Componenti — Moduli — Plugins
- ↳ Template — Grafica
- ↳ Notizie
- ↳ Prodotti Open Source per Joomla!
- ↳ Richieste professionali
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Joomla! 2.5.x
- ↳ Joomla! 1.x
- ↳ Latvian Forum
- ↳ Lithuanian Forum
- ↳ Joomla! 4.x
- ↳ Joomla! 1.5
- ↳ Joomla! 1.7 / Joomla! 1.6
- ↳ Joomla! 1.0
- ↳ Vertimai ir Kalba
- ↳ Malaysian Forum
- ↳ Solved
- ↳ Norwegian Forum
- ↳ Informasjon
- ↳ Arkiverte annonseringer
- ↳ FAQ — Ofte spurte spørsmål
- ↳ Arkiv
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Administrasjon/installasjon
- ↳ Migrering/Oppdatering
- ↳ Template, CSS og design
- ↳ Komponenter/moduler/programutvidelser
- ↳ Sikkerhet
- ↳ Generelt
- ↳ Netthandel, betaling m.m.
- ↳ VirtueMart
- ↳ Andre nettbutikkløsninger
- ↳ Generelt
- ↳ Oversettelser
- ↳ Fremvisning av sider (Show off)
- ↳ Avviste fremvisninger
- ↳ Diverse (off topic)
- ↳ Kommersiell hjelp ønskes
- ↳ Eldre versjoner av Joomla!
- ↳ Joomla! 1.0
- ↳ Administrasjon/installasjon
- ↳ Template, CSS og design
- ↳ Komponenter/moduler/mambots
- ↳ Sikkerhet
- ↳ Generelt
- ↳ Joomla! 1.5
- ↳ Administrasjon/installasjon
- ↳ Migrering/Oppdatering
- ↳ Template, CSS og design
- ↳ Komponenter/moduler/programutvidelser
- ↳ Sikkerhet
- ↳ Generelt
- ↳ Joomla! 2.5
- ↳ Administrasjon/installasjon
- ↳ Migrering/Oppdatering
- ↳ Template, CSS og design
- ↳ Komponenter/moduler/programutvidelser
- ↳ Sikkerhet
- ↳ Generelt
- ↳ Persian Forum
- ↳ قالب ها
- ↳ مدیریت
- ↳ سوالهای عمومی
- ↳ نصب
- ↳ مامبوت ها
- ↳ ماژولها
- ↳ کامپوننت ها
- ↳ Polish Forum
- ↳ Instalacja i aktualizacja
- ↳ Administracja
- ↳ Komponenty, moduły, wtyczki
- ↳ Szablony
- ↳ Paczta i Podziwiajta
- ↳ Modyfikacje i własne rozwiązania
- ↳ Tłumaczenia
- ↳ FAQ
- ↳ Tips&Tricks
- ↳ Dokumentacja
- ↳ Profesjonalne usługi
- ↳ Portuguese Forum
- ↳ Componentes, módulos e mambots
- ↳ Programação e desenvolvimento
- ↳ Segurança
- ↳ Sites dos usuários
- ↳ Off-topic
- ↳ Tradução
- ↳ Templates
- ↳ Romanian Forum
- ↳ Traduceri
- ↳ Russian Forum
- ↳ Объявления по Joomla!
- ↳ Безопасность Joomla!
- ↳ Joomla 4.x — Задайте здесь свой вопрос по поддержке
- ↳ Joomla 3.x — Задайте здесь свой вопрос по поддержке
- ↳ Общие вопросы/Новичок в Joomla! 3.x
- ↳ Установка Joomla! 3.x
- ↳ Миграция и переход на Joomla! 3.x
- ↳ Расширения для Joomla! 3.x
- ↳ Многоязычные веб-сайты на Joomla 3.x
- ↳ Joomla 2.5 — Задайте здесь свой вопрос по поддержке
- ↳ Общие вопросы/Новичок в Joomla! 2.5
- ↳ Установка Joomla! 2.5
- ↳ Расширения для Joomla! 2.5
- ↳ Русский язык Joomla! 2.5
- ↳ Serbian/Montenegrin Forum
- ↳ Tehnička pitanja
- ↳ Instalacija i početnička pitanja
- ↳ Šabloni
- ↳ Prevod i dokumentacija
- ↳ Ćaskanje
- ↳ Bezbednost
- ↳ Joomla! dodaci
- ↳ Pravna pitanja
- ↳ Arhiva
- ↳ Joomla! Događaji i Zajednica
- ↳ Izlog (spisak) sajtova radjenih u Joomla! CMS-u
- ↳ Profesionalne usluge
- ↳ Slovak Forum
- ↳ Spanish Forum
- ↳ Joomla! 4.x
- ↳ Joomla! 3.x
- ↳ Migración y actualización a Joomla 3.x
- ↳ Versiones de Joomla! obsoletas
- ↳ Joomla! 2.5
- ↳ Joomla! 1.5
- ↳ Extensiones
- ↳ Plantillas (templates) y diseño
- ↳ Idioma y traducciones
- ↳ SEO para Joomla!
- ↳ Seguridad y rendimiento
- ↳ Productos de Código Abierto para Joomla!
- ↳ Servicios profesionales
- ↳ Salón de la comunidad Ñ
- ↳ Swedish Forum
- ↳ Meddelanden
- ↳ Forum Joomla! 4.x
- ↳ Forum Joomla! 3.x
- ↳ Allmänna frågor
- ↳ Användning och administration
- ↳ Installation, backup och säkerhet
- ↳ Komponenter, moduler och plugin
- ↳ Mallar (templates) och design
- ↳ Äldre versioner
- ↳ Forum Joomla! 1.0
- ↳ Allmänna frågor
- ↳ Användning och administration
- ↳ Installation, backup och säkerhet
- ↳ Komponenter, moduler och Mambots
- ↳ Mallar (templates) och design
- ↳ Forum Joomla! 1.7 / Joomla! 1.6
- ↳ Allmänna frågor
- ↳ Användning och administration
- ↳ Installation, backup och säkerhet
- ↳ Komponenter, moduler och plugin
- ↳ Mallar (templates) och design
- ↳ Forum Joomla! 1.5
- ↳ Allmänna frågor
- ↳ Användning och administration
- ↳ Installation, backup och säkerhet
- ↳ Komponenter, moduler och plugin
- ↳ Mallar (templates) och design
- ↳ Forum Joomla! 2.5
- ↳ Allmänna frågor
- ↳ Användning och administration
- ↳ Installation, backup och säkerhet
- ↳ Komponenter, moduler och plugin
- ↳ Mallar (templates) och design
- ↳ Översättning
- ↳ Webbplatser gjorda i Joomla
- ↳ Webbplatser J! 3.x
- ↳ Webbplatser J! 2.5
- ↳ Webbplatser Joomla! 1.7 / Joomla! 1.6
- ↳ Webbplatser J! 1.5
- ↳ Webbplatser J! 1.0
- ↳ Kommersiell hjälp önskas
- ↳ Diverse (off topic)
- ↳ Tamil Forum
- ↳ Thai Forum
- ↳ โชว์เว็บไซต์ของคุณที่สร้างด้วยจูมล่า
- ↳ เคล็ดลับการใช้งานส่วนต่างๆ เกี่ยวกับจ&#
- ↳ คอมโพเน้นท์ โมดูล ปลักอิน ต่างๆ ที่ติดตั
- ↳ อับเดดข่าวสารเกี่ยวกับจูมล่าลายไทย
- ↳ Turkish Forum
- ↳ Duyurular
- ↳ Dersler
- ↳ Genel Sorular
- ↳ Bileşen, Modül, Bot
- ↳ Eklenti Haberleri
- ↳ Temalar
- ↳ Vietnamese Forum
- ↳ Gặp gỡ và giao lưu
- ↳ Joomla Tiếng Việt
- ↳ Cài đặt — Cấu hình
- ↳ Thành phần mở rộng cho Joomla!
- ↳ Hỏi đáp Joomla! 3.x
- ↳ Hỏi đáp Joomla! 2.5
- ↳ Hỗ trợ kỹ thuật
- ↳ Bài viết cũ
- ↳ Thiết kế Template
- ↳ Joomla! 1.5
- ↳ Hỏi đáp Joomla! 4.x
- ↳ Welsh Forum
- Other Forums
- ↳ Open Source Products for Joomla!
- ↳ The Lounge
- ↳ Forum Post Assistant (FPA)
- Joomla! Development Forums
- Joomla! Official Sites & Infrastructure
- ↳ docs.joomla.org — Feedback/Information
- ↳ extensions.joomla.org — Feedback/Information
- ↳ joomla.com — Feedback/Information
- ↳ Sites & Infrastructure — Feedback/Information
- ↳ Archived Boards — All boards closed
- ↳ Design and Accessibility — Archived
- ↳ Quality and Testing — Locked and Archived
- ↳ Joomla! 1.0.x_Q&T
- ↳ Q&T 1.0.x Resolved
- ↳ Known Issues
- ↳ Superseded Issues
- ↳ Archive
- ↳ Q&T 1.0.x Resolved — Archived
- ↳ Known Issues — Archive
- ↳ Superseded Issues — Archive
- ↳ Joomla! 3.x Bug Reporting
- ↳ Third Party Testing for Joomla! 1.5
- ↳ Q&T 1.5.x Resolved
- ↳ Joomla! 1.5 BETA
- ↳ Joomla! 1.5 BETA 2
- ↳ Reaction to the ‘Letter to the community’
- ↳ Reaction to New Project Name
- ↳ Logo Competition
- ↳ Humor, Fun and Games
- ↳ Libraries
- ↳ patTemplate
- ↳ com_connector — Multi Joomla Bridge
- ↳ CiviCRM Support
- ↳ CiviCRM Installation Issues
- ↳ FAQ Archive
- ↳ FAQ Discussion Board
- ↳ 3rd Party Extensions FAQ
- ↳ FAQs not moved
- ↳ 3rd Party/Non Joomla! Security FAQ
- ↳ Joomla! Coding 101
- ↳ Joombie Tools of the Trade
- ↳ Joombie Coding Q/A
- ↳ Joombie Think Tank
- ↳ Joombie Developer Lab
- ↳ Joomla Forge — Archived
- ↳ Non-Profit Organizations and Joomla!
- ↳ Schools and Universities
- ↳ Bangsamoro Forum
- ↳ Joomla! 1.5 Template Contest
- ↳ SMF — Simplemachines.org Forum
- ↳ GPL Discussion
- ↳ Security Announcements — Old
- ↳ Tips & Tricks — Moving
- ↳ Submit Your Suggested Tips & Tricks to Docs.joomla.org now please.
- ↳ Google Summer of Code and GHOP
- ↳ Google Summer of Code 2008
- ↳ Proposed projects
- ↳ Student area
- ↳ Past Google Summer of Code Editions
- ↳ Google’s Highly Open Participation Contest
- ↳ Documentation
- ↳ Suggestions, Modifications, and Corrections
- ↳ Archive
- ↳ 1.5 Archive
- ↳ Suggestions, Modifications & Corrections
- ↳ Submit
- ↳ Feedback and Suggestions
- ↳ Applications for participation in the Development Workgroup
- ↳ Development
- ↳ 1.5 Site Showcase — Archived
- ↳ 1.0 x Site Showcase — Archived.
- ↳ Feature Requests — White Papers — Archived
- ↳ Under Review — Archived
- ↳ Accepted — Archived
- ↳ Not Accepted — Archived
- ↳ Wishlists and Feature Requests — Archive
- ↳ Wishlist Archives — Archived
- ↳ Spanish Forum — Archive
- ↳ Papelera
- ↳ Tutoriales
- ↳ General
- ↳ Salón de la Joomlaesfera hispanohablante
- ↳ Danish Forum — Archive
- ↳ Diskussion af Meddelelser + Sikkerhedsmeddelelser + FAQ
- ↳ Shop.Joomla.org
- ↳ Joomla! 1.6 RC Support [closed]
- ↳ Joomla! 1.0 Coding
- ↳ Core Hacks and Patches
- ↳ Joomla! 2.5 Beta Support
- ↳ People.joomla.org — Feedback/Information
- ↳ Joomla! 1.5 Bug Reporting
- ↳ Joomla! 1.5 Coding
- ↳ Joomla! 3 Beta Support
- ↳ Trending Topics
- ↳ Help wanted in the community
- ↳ templates.joomla.org — Feedback/Information
- ↳ Certification
- ↳ Albanian Forum
- ↳ Azeri Forum
- ↳ Urdu Forum
- ↳ Basque Forum
- ↳ Itzulpenaren inguruan
- ↳ Laguntza teknikoa
- ↳ Belarusian Forum
- ↳ Maltese Forum
- ↳ Hungarian Forum
- ↳ Slovenian Forum
- ↳ Japanese Forum
- ↳ Khmer Forum
- ↳ ពិពណ៌ស្ថានបណ្ដាញជុំឡា
- ↳ ជុំឡាខ្មែរមូលដ្ឋានីយកម្ម
- ↳ Community Blog Discussions
- ↳ JoomlaCode.org
- ↳ Joomla! Marketing and PR Team
- ↳ resources.joomla.org — Feedback/Information
- ↳ Training.Joomla.org
- ↳ OpenSourceMatters.org
- ↳ magazine.joomla.org — Feedback/Information
- ↳ Site Showcase
- ↳ Joomla! 4 Related
- ↳ Joomla! Events
- ↳ Joomla! Ideas Forum
- ↳ Registered Joomla! User Groups
- ↳ Joomla! 2.5 Coding
- ↳ Joomla! 2.5 Bug Reporting
- ↳ User eXperience (UX)
- ↳ Joomla! Working Groups
- ↳ Translations
Table of contents:
There are lots of things that can go wrong when you are installing or updating Joomla 3.x. This tutorial will teach you how to deal with most of those issues and fix everything that is broken. So, if you are experiencing problems when updating or installing Joomla, start channeling your inner Fix-It Felix and follow this guide as close as possible.
Never-ending database installation
There are at least two mentions of the fact that you SHOULD have disabled Magic Quotes in your PHP installation in our Joomla installing guides. These mean features are breaking errors display first and main installation second and that’s why it won’t end. Thankfully, there’s a simple solution that is located at the next issue.
I get Magic Quotes error!
Sometimes your Joomla installation is actually able to survive and signal you about the reason why it cannot be completed. If it happened, you have to disable Magic Quotes in your PHP installation and that’s how you can do it:
First way of disabling Magic Quotes is changing values in php.ini. Find the file on your website and add following strings to it:
magic_quotes_gpc = Off
magic_quotes_runtime = Off
magic_quotes_sybase = Off
extension=pdo.so
extension=pdo_mysql.so
If your hosting provider doesn’t like the fact that you are changing php.ini – ask its support team to turn Magic Quotes off manually.
Second way of disabling Magic Quotes is by addressing php.ini throughout .htacess. Just add there following lines:
php_flag magic_quotes_gpc Off
php_value magic_quotes_gpc Off
Now you have to revisit your Joomla installation screen and actually complete it. If your provider does not like the fact that you changed .htacess – ask them to do it. Also create a support ticket to your hoster if you are continuing to experience problems.
If you are wondering what in the world Magic Quotes are, there’s an answer: Magic Quotes are a process that automatically releases incoming data to the PHP script. This feature has been REMOVED in PHP 5.4.
Display Errors
This is not actually an issue, but it pisses a lot of people off anyway. So, if you don’t want Joomla to tell you when something went wrong by writing it on top of every page – you will like this solution to your problem.
IMPORTANT: There are several ways of fixing this problem. Use the simplest method, in case if it does not work – go for the next one.
Method 1. Global Configuration
The simplest solution ever – go to your Global Configuration menu and disable the parameter called Display Errors.
Method 2. Modifying php.ini
If previous solution did not work, open your php.ini file (you may find it with search in your website root directory or by going for XAMPP manual) and locate following string:
display_errors = On or display_errors = 1
Change this value to:
display_errors = Off or display_errors = 0
You are done. Just make sure to reboot your Apache installation when you are changing php.ini.
Method 3. Changing .htaccess
If the first method did not work and you can not find your php.ini (or do not have access to it), you may try modifying it throughout .htaccess with is located in your website’s root folder. Add this to the file:
php_flag display_errors off
If it did not work, change “off” to “0”.
If neither of these methods worked, you should write a support ticket to your internet provider.
Disabling the Safe Mode
Safe Mode is a php feature that allows system to be more stable and defend against incoming issues. Unfortunately, it is incompatible with Joomla, but fortunately there is a quite simple solution to this problem – editing your php.ini. Add this string to the file:
safe_mode = Off or safe_mode = 0
If you are unable to access your php.ini, there’s still a way for you to do it. Just add this line to .htaccess:
php_admin_flag safe_mode Off or php_admin_value safe_mode 0
Some Apache commands allow you to change this line from the Apache as well.
The command and feature were completely removed from PHP 5.4
Handling the Strict Standards Error
This is a very uncommon problem when it comes to commercial servers, but it may appear when you are installing Joomla on your own computer as a local host. This looks like an entire screen of warnings that begin with or feature this:
Strict Standards: Accessing static property JCache::$_handler as nonstatic
Remember – these are warnings, not critical errors, so instead of fixing them, you can merely change the rules of their appearing. To do this, open your php.ini and set following parameters like this:
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED display errors = Off
Now restart Apache for changes to take effect. If you don’t know how to do this, access your server tutorial or support team.
Defining your output buffering mode
This is not a problem or a warning – it is just a recommendation. But if you noticed that your website is running slow, you may try to improve it by setting Output Buffer on (or setting it off if you are experiencing any troubles). Output buffering is a mechanism for controlling how much output data (excluding headers and cookies) PHP should keep internally before pushing that data to the client.
To enable or disable this mechanism, you will have to edit the following line in php.ini. It has three possible value types:
output_buffering = On output_buffering = Off output_buffering = 4096
While there may be some other value than 4096, it is suggested to you to leave it like this – this is the most stable value when buffer is still being used. Turning it to On will make buffer size unlimited which will make it уму faster, but may decrease stability. Turning it Off will decrease speed, but it is the most stable value at all.
Also, you can try accessing php.ini throughout .htaccess by adding to it this line:
php_value output_buffering X
Where X is the value you need.
Change register_globals from On to Off
There’s a possible security hole in a classic PHP installation and, even though it is quite minor, you’d better try to turn it off. It’s called register_globals and to change its mode, you will have to access php.ini. Find the following string:
register_globals = On
And modify it to look like this:
register_globals = Off
Done!
You may also access it throughout .htaccess by adding the following line to the file:
php_flag register_globals Off
Seeing 500 Internal Server Error
There may be an error you will see on your front-page (or, instead your front-page) that will look like “Error 500: Internal Server Error”). There may be quite a lot of reasons for it to appear, but what is the most important – you, usually, have nothing to do with them. The error means that server is misconfigured and cannot send the data your browser asked for. Also, your server may be under DDOS attack or heavy number of visitors – if this is the reason (you can ask your hoster about that) – you may want to buy faster and more protected server.
This is a list of possible reasons of 500 Internal Server Error:
- Misconfigured web server file or folder read and write permissions — check your php.ini and .htaccess files.
- Corrupted file(s).
- Script issues
Blank screen after upgrading to Joomla 3.2
Joomla 3.2 brought a lot of changes, but what is the most important for you – new requirements for servers and extensions. It means, that if your website or your server is incompatible with Joomla 3.2, but you still upgraded it – you are in for a lot of trouble. Blank screen means that your system tries to tell you something through display_errors mechanism, but fails. But there is a solution to the problem:
Joomla will tell you to turn on display_errors, and while it is needed too, it is not the complete solution. Find a file called configuration.php in root folder of your website and open it. Now you need this string:
public $error_reporting = ‘default’
But default is not enough. Change the value of the string to “maximum” so it will look like this:
public $error_reporting = ‘maximum’
IMPORTANT: Do NOT copy the line from here – formatting systems of web and php file are different (for example, in web and other documents there are two types of apostrophe, while php recognizes only one).
Now refresh your website page and see the real problem you need solution for!
Increasing PHP upload limit
There are times when your system can not finish the installation for what looks like broken installation package, but on your PC you can unpack it without any trouble. It means that your server is misconfigured or very weak. If it is the former, there is a solution. There are four strings that defy the limits of uploading files on server in php.ini file. They are:
- post_max_size
- upload_max_filesize
- max_execution_time
- memory_limit
If you are experiencing any problems with uploading files, you will need to change them throughout .htaccess or directly (sometimes your hosting provider does not allow .htaccess overrides). To do this the first way, open .htaccess and add following strings:
php_value post_max_size 8M php_value upload_max_filesize 8M php_value max_execution_time 60 php_value memory_limit 128M
These values are Joomla recommended settings. You may want to change them, but then you are on your own for any trouble that comes in.
If you do not have access to .htaccess, you may do it another way – by changing the lines in php.ini directly. Make them accept these values:
Make them accept these values:
post_max_size = 8M upload_max_filesize = 8M memory_limit = 128M max_execution_time = 60
This should fix inability of your server to unpack or upload Joomla. If the error continues – check FTP permissions of tmp directory – it should have at least 755.
Where is the php.ini file?
There is quite a lot of locations for your php.ini to be in. It depends on your server, server version and you hosting provider’s settings. Here is a list of the most common locations of php.ini:
- cPanel: On cPanel Shared Servers php.ini is located in Joomla root file directory. cPanel may have a special wizard for you in the Software services section.
- Parallels Plesk Panel: /etc/php.ini
- XAMPP: C:xamppphpphp.ini
- Ubuntu: /etc/php5/apache2
- GoDaddy servers: You need to create your own and place it in the Joomla root directory
If you are running PHP5 instead of PHP4, your php.ini file will be called php5.ini
IMPORTANT: MacOS has a security policy that defies files with names that begin with «dot» symbol as system files and thus sets them as hidden and refuses to display the in Finder. If you are using third party software, like FTP client, there may be a way to go around this problem. For example, CyberDuck has a special mode called «Show hidden items».
Failed to connect to your MySQL database server
If you are getting this error, it means that your Joomla installation script is unable to connect to MySQL database. Check once more if the username, password, hostname and database name are valid.
IMPORTANT: In most cases hostname is localhost, but some providers dew to internal reasons, change it to something else. If you are getting this message and you are sure that everything else is alright, ask your provider support team about the hostname.
CMS Joomla 3.0 была разработана для работы на веб-серверах под управлением LAMP или Windows and IIS. Тем не менее, у Вас могут возникнуть проблемы при установке Joomla 3.0 из-за разных версий установленного программного обеспечения или аппаратной конфигурации.
В этой статье Я расскажу вам какие могут возникнуть проблемы во время установки Joomla 3.0 и как их можно решить. Заметное улучшение интерфейса Joomla 3.0 по сравнению с бетой.
Оглавление
- 1 Версии Серверного программного обеспечения
- 2 Magic Quotes GPC
- 3 How to disable the safe mode — Как отключить safe mode (безопасный режим)
- 4 Установка Joomla 3 на хостинг ТаймВеб
- 5 How to disable Output Buffering — Как отключить Output Buffering (Буферизация вывода)
- 6 Failed to connect to your MySQL database server — Не удалось подключиться к серверу баз данных MySQL
- 7 Cannot write to configuration to configuration.php — Невозможно записать в файл конфигурации configuration.php
- 8 «500 Internal Server Error» error — «500 Internal Server Error» Ошибка
Версии Серверного программного обеспечения
У Вас может возникнуть проблема при установке последней версии Joomla 3, так как она имеет более высокие требования к Вашему программному обеспечению на хостинге, где будет располагаться Ваш сайт. Joomla 3.0 нуждается в более новых версиях PHP или MySQL. Настоятельно рекомендуется установить Веб-сервер Apache. Кроме того, вы должны иметь версии как минимум PHP 5.3.1 и MySQL 5.1 или PostgreSQL 8.3.18. Даже если на Вашем хостинге установлено устаревшее программное обеспечение PHP и MySQL по умолчанию, Вы можете изменить конфигурацию сервера с помощью настройки файла «. htaccess».
Magic Quotes GPC
Если при установке система не позволяет Вам продолжить установку Joomla 3 потому, что Magic Quotes GPC «ВКЛЮЧЕН», то Вам нужно его выключить в положение «OFF». Magic Quotes GPC может быть включена или отключена в файле php.ini, просто изменив значение magic_quotes_gpc с «включен» на «выключен». Вы можете просто создать файл php.ini с помощью следующего кода: magic_quotes_gpc = Off или magic_quotes_gpc = 0. Если у вас нет доступа к файлу php.ini, обратитесь за помощью к системному администратору Вашего хостинга за помощью.
How to disable the safe mode — Как отключить safe mode (безопасный режим)
Отключение безопасного режима (safe mode) в PHP, это попытка решить на совместно используемых серверах проблемы безопасности. Этот режим очень просто отключить на всем сервере. Все, что вам нужно сделать, это просто отредактировать файл php.ini и добавить safe_mode = Off или safe_mode = 0. Эта функция стала устаревшей в PHP 5.3.0 и удалена из PHP 5.4.0. Вы можете в файл htaccess вставить эту строку в файл Htaccess: php_admin_flag safe_mode Off или php_admin_value safe_mode 0. Есть несколько директив Apache, которые позволяют изменять конфигурацию PHP внутри файла конфигурации Apache себя.
У меня тоже возникла такая проблема при установке Joomla 3.0.
Не был отключен режим safe mode (безопасный режим). И вариант с прописыванием настроек в файл htaccess не помог.
Но Я решил эту проблему. Мои сайты находятся на хостинге ТаймВеб и на этом хостинге есть возможность ручного переключения версии программного обеспечения сервера. Я просто выбрал самую новую версию и Joomla 3.0 сразу начала устанавливаться.
Если Вам не понятно, что именно и как Я сделал, сообщите мне на почту или в комментариях к статье и Я напишу подробную статью и создам Видеоурок по установке Joomla 3.0.
Установка Joomla 3 на хостинг ТаймВеб
How to disable Output Buffering — Как отключить Output Buffering (Буферизация вывода)
Буферизация вывода представляет собой механизм, который управляет объемом буфера, сколько выходных данных (за исключением заголовков и куков) PHP должны иметь объем буфера перед отправкой данных клиенту. Отредактируйте ваш php.ini файл и добавьте output_buffering: output_buffering = 4096 или output_buffering = Off. Вы можете попробовать также отредактировать файл htaccess добавив в него: php_value output_buffering Off
Failed to connect to your MySQL database server — Не удалось подключиться к серверу баз данных MySQL
Программа установки Joomla 3.0 не может подключиться к базе данных. Проверьте имя пользователя, пароль и имя хоста, которые Вы создали ранее.
Cannot write to configuration to configuration.php — Невозможно записать в файл конфигурации configuration.php
Сценарий установки Joomla 3.0 требует права на запись в файл конфигурации configuration.php. Иногда, установка Joomla на Linux приводит к тому, что установщик приложений не имеет права создавать или изменять файлы.
«500 Internal Server Error» error — «500 Internal Server Error» Ошибка
«Internal Server Error» — нет доступа к серверу, сайту. Этот сервер настроен неправильно. Эта ошибка часто встречается на:
Неправильно настроенном веб-сервере. Файл или папка не доступна на чтение и запись — проверьте ваш php.ini и htaccess файлы и не повреждены ли файлы.
Просмотров: 227
Quickstart Installation Problems and How to fix them
- Last Updated:
- June 16th, 2015
- Category:
- Quickstart
Unfortunately, sometimes even the most carefully prepared quickstart package may cause problems, especially during a Joomla 3.x installation. That’s why we always suggest you use the latest stable versions of PHP (5.4+). In this manual you’ll find answers for most common problems during installation or after installation.
Deprecated: preg_replace(): The /e modifier is deprecated
If during installing the gk_template_quickstart_J!25.zip (Quickstart with Joomla 2.5 on board) on server or xampp, after selecting the language there appear such an error, which prevent further installation.
You have to change PHP version from v5.5 to 5.4, because joomla 2.5 is not fully ready for new version. The problem is that the Joomla! 2.5.x installation sometimes cannot continue when PHP 5.5 is used.
Please change this PHP settings:
- In most cases in Hosting Panel
- Sometimes using php.ini file or ask Hosting support
- Or you have to use “older” Xampp 1.8.2-2 version (based on PHP 5.4)
Alternative solution (if you have to use PHP 5.5 anyway) would be a small modification in this file: libraries/joomla/filter/input.php – new changed file you should find here on github.com. Download file: input.zip(unzip before override).
Never-ending database installation
If you’ve been trying to install a package with a template gk_template_quickstart_J!3.zip or gk_template_quickstart_J!25.zip and the installation hangs on the “Creating configuration File” step and returned to the Overview, as in the image below…
…you have to make few changes in order to fix it. I saw that sometimes problems appeared when I was using Adblock Plus for my web browser, so please disable it for a while. If this doesn’t help let’s try the next tip.
Please check your PHP settings:
Turn Off Display Error PHP.ini
It must be disabled. You can set PHP error reporting off in the php.ini file (in case you have access to this file).
Amend the display_errors line to off: display_errors = Off
If you have installed your server with the help of XAMPP, check the documentation for information on where to find the php.ini file. Don’t forget to stop Apache server before doing any modifications and start it again after saving these modifications.
If you have no access to the php.ini file but you can modify the .htaccess file on your server (found in the root of your public_html folder – your Joomla! 3.x site), try to add the following code there: php_flag display_errors off. If your modifications in this file have no effects, try asking your webhosting provider to disable error reporting.
If you don’t have the ability to change it, especially for Joomla 2.5, then in the /installation folder inside the index.php file at the beginning (line ~13) please add:
ini_set('display_errors', 0);
– upload the changed file and try to install again!.
Magic Quotes
It’s preferable to disable this also; if it is enabled you will probably get problems with saving module settings. Magic Quotes is a process that automatically releases incoming data to the PHP script. This feature has been REMOVED in PHP 5.4.
To disable it use
magic_quotes_gpc = Off magic_quotes_runtime = Off magic_quotes_sybase = Off
inside php.ini or you can also try to add these two lines inside .htaccess:
php_flag magic_quotes_gpc Off php_value magic_quotes_gpc Off
If your modifications in this file have no effects, try to ask your webhosting provider to disable Magic Quotes.
Second tip: Increase PHP memory limit
A PHP memory limit of 32MB is the minimum requirement for Joomla! and 64MB is recommended for Quickstart installations. Locate the php.ini file used by your web server. Note that this change will affect all CMS websites and PHP scripts on the server. Add or Edit the memory_limit parameter in the php.ini file:
memory_limit = 64M ;
Add the following line to a php.ini file in your Website root folder. If there is no section already for this, place the above line at the end of the file.
In some shared hosting environments, access to the PHP memory limit setting is restricted. If you cannot make the change yourself, please ask your hosting provider to adjust it for you, or look for a new host that allows more flexibility.
Third tip: Increase Max execution time
This sets the maximum time in seconds a script is allowed to run before it is terminated by the parser. Please check php.ini file (using wampmanager!! gets you to the right file) and look for “max_execution_time = 60” and change it to 240 or more. Then the installation should work perfect.
Four tip: Manually installation
If you still have the same “never-ending” installation process problem you have to use you client FTP to do some additional steps:
- Write down what prefix to the database was used (on notepad).
- Rename or, a better option, delete the /installation – folder.
- Create a new configuration.php file and put all following data in it:
public $offline_message = 'This site is down for maintenance.';
public $display_offline_message = '1';
public $offline_image = '';
public $sitename = 'gk_creative__J30';
public $editor = 'tinymce';
public $captcha = '0';
public $list_limit = '20';
public $access = '1';
public $debug = '0';
public $debug_lang = '0';
public $dbtype = 'mysql';
public $host = '-------localhost or ???-------';
public $user = '-----MySQL user-------';
public $password = '----MySQL password ---------';
public $db = '---------MYSQL data base-------';
public $dbprefix = '----your--prefix-----';
public $live_site = '';
public $secret = 'qLgqKaKKj7piuE1C';
public $gzip = '0';
public $error_reporting = 'default';
public $helpurl = 'http://help.joomla.org/proxy/index.php?option=com_help&keyref=Help{major}{minor}:{keyref}';
public $ftp_host = '';
public $ftp_port = '';
public $ftp_user = '';
public $ftp_pass = '';
public $ftp_root = '';
public $ftp_enable = '';
public $offset = 'UTC';
public $mailer = 'mail';
public $mailfrom = '[email protected]';
public $fromname = 'gk_creative_J30';
public $sendmail = '/usr/sbin/sendmail';
public $smtpauth = '0';
public $smtpuser = '';
public $smtppass = '';
public $smtphost = 'localhost';
public $smtpsecure = 'none';
public $smtpport = '25';
public $caching = '0';
public $cache_handler = 'file';
public $cachetime = '15';
public $MetaDesc = '';
public $MetaKeys = '';
public $MetaTitle = '1';
public $MetaAuthor = '1';
public $MetaVersion = '0';
public $robots = '';
public $sef = '1';
public $sef_rewrite = '0';
public $sef_suffix = '0';
public $unicodeslugs = '0';
public $feed_limit = '10';
public $log_path = '/logs';
public $tmp_path = '/tmp';
public $lifetime = '15';
public $session_handler = 'database';
}
Of course, now you have to change MySQL and the prefix value (!) to make it work. Now your Joomla 3.1 website should work. You may check, but please complete these final steps -> unlock super administrator account.
- Navigate to phpMyAdmin and select the database for the Joomla! 3.x site in the left-hand drop-down list box. This will show the database tables on the left side of the screen.
- Click on the table “prefix_users” in the list of tables (note: you may have a prefix that is not jos_, simply go to the _users table for your prefix).
- Change the value in “block” from 1 to 0.
- Change your password
- Save changes. Now you can log into the back-end using your new access data.
When I click “next” in (Language settings), nothing happens
To fix it you have to modify a small part of one file in the Joomla 3.1 installation folder. This is completely safe. Please rename the class ‘InstallationViewFTP’ to ‘InstallationViewFtp’ in line 17.
class InstallationViewFtp extends JViewLegacy
You will find this class in the installation/views/ftp/view.html.php .
Then run again your installation process; all steps should now complete. This bug will likely be fixed in the next version of Joomla! 3.2.4 or Joomla! 3.3.
I can not login to back-end after Quickstart installation
If you finished all steps of installation without any error but you still can not login because your administrator username or password was not accepted. First make sure you use the same capitalization you used when you entered the access data. Passwords in Joomla! are case-sensitive, and you need to enter them exactly as they were created.
Second reason, this error stems from the fact that you might have set”admin” as username. Most Joomla! Quickstart use the default user name “admin” without the quotes. Because of that in most cases it cause no access problem with warning message. To avoid this you DO NOT USE “admin” USERNAME DURING QS INSTALLATION. If you did this – you have to re-install quickstart again – this is the simplest method – and insert different Username (for example “[email protected]”). Sure, you can change via PHPMyAdmin – but it request some knowledge and it’s not recommended for beginners.
Note: To avoid this you need to ensure that every new created user account for Super Administrator has a unique Username. Use your own new administrative account data instead default “admin” or “gkadmin”.
Remember that: A CMS with a too simple username & password for the Administrator account is highly vulnerable to all sorts of hacker attacks. If you have a weak password, the question is not so much if it will be exploited, but if it has already been exploited.
Quickstart Installation Problems and How to fix them 4.155 (83.00%) 20 votes
This article was first published July 3rd, 2013
← Back
0 Пользователей и 1 Гость просматривают эту тему.
- 19 Ответов
- 4018 Просмотров
Доброго времени суток, друзья!
Так, как я пока еще новичок не могу разобраться в одной возникшей проблеме. При установке Joomla 3.7.4 на хостинг, у меня выскочило такое предупреждение —
«Warning ; You are trying to use a database host which is not on your local server. For security reasons, you need to verify the ownership of your web hosting account. Please read the documentation for more information»
, и за счет этого не устанавливается Joomla.
Рекомендация заключается в том, чтобы создать файл в папке установки для подтверждения, что я являюсь владельцем веб-сайта. Прошу помощи разобраться в этой нелегкой ситуации 
Также ниже указан оригинал текста рекомендации Joomla.
«If you want to install 3.7.4 and want to use a remote database server we require you to delete a file in the installation folder that was randomly created by the installer. As this filename is unique to your session we are sure you just deleted the file and we can finish installing as normal.
A special case is the “FTP mode”. In that case Joomla is not able to create files. So we require you to create a file in the installation folder in order to confirm that you are the website owner.
In both cases, the file name will be displayed in a message on your screen with instructions on how to validate the installation.»
Заранее спасибо.
а как вы устанавливаете? и откуда скачали саму Joomla
Записан
SEO-оптимизация,продвижение
Создание и сопровождение сайтов на Joomla
Миграция
Устанавливаю закачивая на сервер через Filezilla, а саму Joomla скачала с официального сайта.
Устанавливаю закачивая на сервер через Filezilla, а саму Joomla скачала с официального сайта.
С официального это с какого?
Записан
Оказываю услуги по Joomla | Миграция на Joomla 3.x | Сопровождение | IT-аутсорсинг | Недорогие домены и хостинг
закачали. распаковали(если в архиве)
домен создан? база данных создана?
если да——
набираем название сайта — пошла установка
всяких файлов закинуть для подтверждения Joomla не просит(насколько я знаю и сколько раз ставил не видел)
Записан
SEO-оптимизация,продвижение
Создание и сопровождение сайтов на Joomla
Миграция
С этого — https://downloads.joomla.org/ru/
Да, это официальный сайт. Теперь вопрос про хостинг. Вы уверены, что хотите использовать сервер удаленных баз данных? Вы корректно задали настройки? Если ваша база данных не находится на том же сервере, что и сайт, Joomla проводит дополнительную проверку, которая якобы гарантирует, что вы являетесь владельцем веб-сайта и защищает установку.
См. тут
Записан
Оказываю услуги по Joomla | Миграция на Joomla 3.x | Сопровождение | IT-аутсорсинг | Недорогие домены и хостинг
Абсолютно все создано и домен, и база данных…
Все делала как Вы пишите, но при установке на верху появилось такое предупреждение о, котором писала выше. После заполнения всех полей, нажимаю установку…она как бы идет, но не загружается полностью. Может быть это из за данного предупреждения?
Скорее всего вы неправильно задаете параметры базы.
Либо, как вариант, попробуйте удалить папку installation и залить ее заново, так же удалить configuration.php, если он был создан. При установке при запросе что делать с имеющимися таблицами ставьте — перезаписать.
« Последнее редактирование: 08.08.2017, 13:46:10 от SeBun »
Записан
Оказываю услуги по Joomla | Миграция на Joomla 3.x | Сопровождение | IT-аутсорсинг | Недорогие домены и хостинг
Да, это официальный сайт. Теперь вопрос про хостинг. Вы уверены, что хотите использовать сервер удаленных баз данных? Вы корректно задали настройки? Если ваша база данных не находится на том же сервере, что и сайт, Joomla проводит дополнительную проверку, которая якобы гарантирует, что вы являетесь владельцем веб-сайта и защищает установку.
См. тут
Я смотрела, но не могу понять, что за файл я должна создать в папке установки для подтверждения прав на сайте….
Я смотрела, но не могу понять, что за файл я должна создать в папке установки для подтверждения прав на сайте….
In both cases, the file name will be displayed in a message on your screen with instructions on how to validate the installation.
То есть название файла должно отображаться в том сообщении, о котором идет речь. Я это сообщение в глаза еще не видел, поэтому ориентируюсь только на инструкцию, ссылку на которую дал выше.
Записан
Оказываю услуги по Joomla | Миграция на Joomla 3.x | Сопровождение | IT-аутсорсинг | Недорогие домены и хостинг
Наверно сервер БД не localhost
Читал об этом, но пока не сталкивался.
Если не хочется разбираться что и откуда удалять — просто поставьте 3.7.3 и тут же обновите
ну что то мне кажется что с 3.7.3 будет также петрушка
а сервер БД точно не локальный
специально сейчас проверил(выскакивает тоже самое)
Записан
SEO-оптимизация,продвижение
Создание и сопровождение сайтов на Joomla
Миграция
ну что то мне кажется что с 3.7.3 будет также петрушка
а сервер БД точно не локальный
специально сейчас проверил(выскакивает тоже самое)
Нет. Это нововведение появилось в 3.7.4, починят в 3.8.0
Ребята, аларм!
Эта ситуация распространённая.
Сегодня не смог установить Joomla 3.7.4 из дистрибутива на серверах виртуального хостинга Peterhost (серверы БД на виртуалках — удалённые).
Установка «зависает» на «Создание файла конфигурации».
Консоль молчит.
Полный трындец…
Ребята, аларм!
Эта ситуация распространённая.
Сегодня не смог установить Joomla 3.7.4 из дистрибутива на серверах виртуального хостинга Peterhost (серверы БД на виртуалках — удалённые).
Установка «зависает» на «Создание файла конфигурации».
Консоль молчит.
Полный трындец…
собссно
Если не хочется разбираться что и откуда удалять — просто поставьте 3.7.3 и тут же обновите
В этом то и шляпа — при попытке обновления с версии 3.7.3 получаю ошибку на всех серверах:
0 Failed to connect to downloads.joomla.org port 443: Connection timed out
получаю ошибку на всех серверах…
Что значит серверах? У вас один хостер или разные? Вы же написали, что хостер Peterhost… Поставьте 3.7.3 и ждите 3.8.0, как вариант. Если хотите решить вопрос, я выше давал ссылку на официальный док.
« Последнее редактирование: 14.08.2017, 15:49:32 от SeBun »
Записан
Оказываю услуги по Joomla | Миграция на Joomla 3.x | Сопровождение | IT-аутсорсинг | Недорогие домены и хостинг
Что значит серверах? У вас один хостер или разные? Вы же написали, что хостер Peterhost… Поставьте 3.7.3 и ждите 3.8.0, как вариант. Если хотите решить вопрос, я выше давал ссылку на официальный док.
Я написал про Peterhost, что касается новых установок.
А про обновления — такой на RU Center и на Peterhost
3.7.5 вышла.
Единственный фикс в ней — как раз работа с удаленными БД при установке.
Installation Errors
HikaShop installs files in the following folders. Please first make sure those folders are writable before trying to install HikaShop :
- Joomla / Administrator / Components
- Joomla / Components
- Joomla / Modules
- Joomla / Plugins
- Joomla / Plugins / Hikashop
- Joomla / Plugins / Hikashoppayment
- Joomla / Plugins / Hikashopshipping
- Joomla / Plugins / Acymailing
- Joomla / Plugins / Search
- Joomla / Plugins / User
- Joomla / Plugins / System
- Joomla / Language / en-GB
- Joomla / tmp
- Joomla / media
In Joomla 3, you can check the folder permissions in the Joomla backend, under: System > System Information > Folder permissions
If you have errors regarding the copy of files, it’s likely to be because of access right issues. You should look at these documentation pages of Joomla:
- Why can’t you install any extensions? (docs.joomla.org)
- Installing an extension (docs.joomla.org)
- How to solve Installation errors Extension Manager (docs.joomla.org)
Blank page
A blank page does not help us to determine what could be the problem so if you get a blank page (an entire white screen without anything written on it).
Please make sure that your PHP configuration enables you to see errors and if not, edit your php.ini file and search for the string parameter display_errors.
This parameter should be turned On: display_errors = On.
If it’s not the case, please edit your php.ini file, modify this line, save your file and then restart your server and try again to install HikaShop. You should not see a blank screen anymore and the error message will help us a lot to fix the problem.
In the Joomla global configuration (System > Global configuration), you can also change temporally the setting Error reporting (under tab “Server”) to development
If you can not see any error, please try to install HikaShop via FTP, it solves more than half of the installlation issues.
Install via FTP
If you have difficulties to install HikaShop, you may want to try to install it via FTP.
This way, Joomla won’t have to upload the HikaShop package on your website so the installation will be much faster.
- Extract your HikaShop package in a folder called “hikashop” on your own computer.
- Open your FTP software (FileZilla for example), connect to your website and upload the folder “hikashop” in the temporary folder of your website : /tmp/
- Go to your Joomla Installer manager on your website backend and specify the path of your folder in the input “Install from Directory” : “home…tmphikashop”.
- Click on the button “Install”… the install process should be much faster and will enable you to successfully install HikaShop.
-1 – an error has occurred ( It was not possible to copy the selected file. )
This error message is displayed when Joomla can not copy a folder from the temp folder to the destination folder.
It’s usually because of access rights and you should make sure the HikaShop folders are writeable (see above).
If it does not solve the issue, please edit the file libraries/joomla/filesystem/folder.php
Around line 93 AND 122, please replace:
return JError::raiseError(-1, JText::_(‘Copy failed’));
by
return JError::raiseError(-1, JText::_(‘Copy failed’).’ ‘.$sfid.’ => ‘.$dfid);
It won’t solve the problem but at least if you try to install again HikaShop, you will see a much better error message telling you what folder is not writeable.
That way you can move forward by fixing the permission issue on that folder and install again HikaShop.
This kind of error can be automatically solved by enabling the FTP layer on the Joomla configuration page (or turning it OFF if it was enabled).
- Component Install: DB function reports no errors
- JFTP: :delete: Bad response
- JFTP: :delete: Bad response
- Error installing component
This error is apparently due to the fact HikaShop could not be installed properly and there are probably still some instances of HikaShop on your Extensions Manager.
Please go on your Extensions Manager (click on the menu “Manage”), select HikaShop (the component) and uninstall it.
If it can’t be uninstalled from there, please access your phpMyAdmin and execute this query:
- DELETE FROM `jos_menu` WHERE link LIKE ‘%com_hikashop%’;
- DELETE FROM jos_extensions WHERE element = ‘com_hikashop’;
- DELETE FROM jos_assets WHERE name=’com_hikashop’;
Then install HikaShop again… it should work.
- JFolder: :files: Path is not a folder. Path: xxxxxxxxxxxxxx/tmp/install_xxxxxxxx
- JFolder: :folder: Path is not a folder. Path: xxxxxxxxxxxxxx/tmp/install_xxxxxxxx
- JFolder: :files: Path is not a folder. Path: xxxxxxxxxxxxxx/tmp/install_xxxxxxxx
- JInstaller: :Install: Cannot find Joomla XML setup file
These errors can happen even though your access rights are correctly configured. It comes apparently from a problem between the ZIP extraction library and your server settings. You should try to convert the installation package of HikaShop to a tar.gz file with 7zip (tool for windows to generate packages) or an equivalent tool and then use that tar.gz package instead in order to install HikaShop.
From: https://www.hikashop.com
We’re a Digital Team from EngineTemplate with 5 content experts. Our team has 5 years exp in open source Joomla and WordPress, we make daily blogs and build useful resources for everyone who is having issues with open source while using it.
Successfully installing any Joomla! component / plugin / module depends on many factors and the process may be interrupted by a number of reasons. In this article we will be providing explanations and solutions for all possible situations.
Article Sections
- Folder Permissions
- FTP upload and the Install from Directory feature
- Blank page
- -1 — An error has occurred. Copy failed /
- Warning: Failed to move file!
- Unable to write entry — JInstaller: :Install: Cannot find Joomla! XML setup file
- Please enter a package directory
- JFolder::create: Path not in open_basedir paths — Unable to create destination
- Component Install: DB function reports no errors
- Error Building Admin Menus
- JTableMenu::_getNode Failed
Folder Permissions
The most common factor that intervenes in the installation process is how permissions are set for some key folders, in which components usually place their files.
Please make sure that you have enough read / write permissions set for the following Joomla! installation folders:
/tmp — Joomla! copies all uploaded files in this folder, it is absolutely necessary that it is writeable
/administrator/components — component backend files are being placed here
/administrator/language — backend language files for all extension types (components / plugins / modules) are being placed in this folder
/administrator/modules — all backend area modules are installed here
/administrator/manifests — manifest files (files used to guide the installation process) will be placed in this folder
/components — component frontend files are stored in this folder
/language — frontend language files for all extension types (components / plugins / modules) can be found here
/modules — frontend modules will be installed here
/plugins — all plugins are being installed in this folder
/media — some extensions place files in this folder. It is mainly used for media files, such as images or videos.
Notes:
- In order to find out for which folders you need to verify permissions (for a certain extension) simply open the extension’s installation package (.zip archive) and analyze it’s folder structure.
- Each of our components has its own Installing and uninstalling documentation section where all folders (related to it) that require 755 permissions are listed.
FTP upload and the Install from Directory feature
If you are having trouble uploading the installation package (through the default Extensions >> Extension Manager >> Upload Package File feature), you can simply upload the files on your website via FTP and install the component from there:
- Extract the installation package (archive) into a folder (which can be named in any way you like) and upload this folder in the Joomla! installation’s default tmp folder via FTP (using a FTP file manager like FileZilla).
- Head to Extensions >> Extension Manager >> Install from Directory, provide the path to the uploaded folder and click on Install. Joomla! will automatically retrieve the needed files from the specified location.
Blank page
When attempting to install an extension through the default Extensions >> Extension Manager >> Upload Package File feature you might get a blank page after clicking on Upload & Install. If this is the case, you will need to check whether your PHP is configured in such manner that it displays errors or not, as it is necessary to know what error is being returned by PHP in order to find a solution.
To do so, head to Site >> System Information >> PHP Settings and check if Display Errors is marked as On. If you find it to be marked as Off, please edit your php.ini file on your server and set display_errors to On. Note that you will need to restart your server in order for this to work. There are 2 solutions for your issue:
- Head to Site >> Global Configuration >> Server and set Error Reporting to Development. Now Joomla! will report all errors and warnings as they occur.
- As it is very likely that you do not have access to the server’s php.ini file, you can add the following code at the top of your index.php file:
The code will activate the display_errors option for your website.
-1 — An error has occurred. Copy failed /
This occurs when Joomla! fails to copy a file / folder from the tmp folder to it’s destination. It is, most likely, generated by the fact that there are not enough write permissions set up for the destination folder. To fix this, simply make sure that there are enough permissions set for the destination folder.
|
|
In Joomla! 3.x:
- edit the libraries/src/Filesystem/Folder.php file
- look for the following code (around lines 155-159):
- and replace it with this one:
if (!@copy($sfid, $dfid)) { throw new RuntimeException('Copy file failed', -1); }
if (!@copy($sfid, $dfid)) { throw new RuntimeException('Copy file failed '.$sfid.' => '.$dfid, -1); }
The code above will improve how the error message is displayed by adding the source and destination folders to it. This way, you will be able to know exactly which folders do not have enough permissions set.
Warning: Failed to move file!
This error occurs when Joomla! does not manage to move a file from the server’s tmp folder to your website’s tmp folder. This may be caused by incorrectly set up permissions or wrongly provided path to the tmp folder.
|
|
Another solution to this would be to first unzip the package contents, upload them via FTP in one or your website’s folders, and then install the package via the Extensions >> Extension Manager >> Install from Directory feature.
Unable to write entry — JInstaller: :Install: Cannot find Joomla! XML setup file
All extensions are installed based on an XML file which provides destinations for all of the component’s files and folders. If this file cannot be found (because the .zip package could not be extracted), you will get this error message.
The solution to this problem is to install the extension as explained in this article’s FTP upload section.
|
|
Please enter a package directory
When installing an extension via FTP upload, providing an incorrect path (or none at all) to the folder which contains the extension’s installation files will render Joomla! to throw this error message. Please apply the following in order to identify the correct path to use:
- edit the libraries/joomla/filesystem/install.php file
- look for the following code (around lines 198-201):
- and replace it with this one:
if (!is_dir($p_dir)) { JError::raiseWarning('', JText::_('COM_INSTALLER_MSG_INSTALL_PLEASE_ENTER_A_PACKAGE_DIRECTORY')); return false; }
if (!is_dir($p_dir)) { JError::raiseWarning('', JText::_('COM_INSTALLER_MSG_INSTALL_PLEASE_ENTER_A_PACKAGE_DIRECTORY').' | Example : '.JPATH_SITE.DS.'tmp'); return false; }
|
|
JFolder::create: Path not in open_basedir paths — Unable to create destination
This occurs when the path to the tmp folder was provided incorrectly in Joomla!’s configuration (Site >> Global Configuration >> Server >> Path to Temp Folder field).
To fix the issue, make sure to specify the absolute path to the tmp folder. Another solution would be to install the extension through FTP upload.
|
|
Component Install: DB function reports no errors
JFTP: :delete: Bad response
JFTP: :delete: Bad response
Error installing component
The present error occurs when an extension was improperly installed. When this happens, some instances of the extension remain recorder in the database.
|
|
Head to Extensions >> Extension Manager >> click on Manage >> select the extension and click on Uninstall.
After doing so, open your database manager (for example, phpMyAdmin) and run the following query:
After doing so, please try reinstalling the extension.
Remember to:
- Replace #_ with your database’s actual prefix
- Replace component (in com_component) with the actual name of your component. This is also available for plugins (plg_plugin) and modules (mod_module).
Error Building Admin Menus
This is only available for components, not plugins and modules. When this occurs, the component will be installed successfully but you will not be able to access it in the Components menu. To fix the problem, open your database manager (like phpMyAdmin) and run the following query:
Try reinstalling the component after running the query, it should appear in the Components menu this time.
|
|
Remember to:
- Replace #_ with your database’s actual prefix
- Replace component (in com_component) with the actual name of your component.
JTableMenu::_getNode Failed
The result to this issue is the same as above, the component will not show up in the Components menu. However, the cause is different: the root item from the #__menu table(with id=1) is missing from the database. If the root menu no longer exists, Joomla! will not be capable of locating it’s subsidiary menus.
|
|
To fix the issue, first run the following query in your database manager:
Joomla! 3.x
INSERT INTO `#__menu` (`id` ,`menutype` ,`title` ,`alias` ,`note` ,`path` ,`link` ,`type` ,`published` ,`parent_id` ,`level` , `component_id` ,`checked_out` ,`checked_out_time` ,`browserNav` ,`access` ,`img` ,`template_style_id` ,`params` , `lft` ,`rgt` ,`home` ,`language` ,`client_id` ) VALUES ( '1', '', 'Menu_Item_Root', 'root', '', '', '', '', '1', '0', '0', '0', '0', '0000-00-00 00:00:00', '0', '0', '', '0', '', '0', '0', '0', '*', '0')
then try installing the component one more time.
14 persons found this article helpful.
Was this article helpful?
Yes
No