Why failure? I have gotten no explanation why I am unable to dump the remote database other than
"It's too big" or "It's the wrong version". I am able to dump other databases
at that host so I know there's no issue at my end or with the phpmyadmin the host provides.
I'm in the middle of
Thanks! Now to see if I can at least export those tables. [I've had three
support tickets with the shared host, two of which were escalated, that have
all failed to provide a solution.] Off to phpmyadmin land.
___
TYPO3-english mailing list
I am stuck by a shared host that cannot seem to provide a dump of the MySql
database. The claim is that the database is in version 4 and all of their
client tools available to me (phpmyadmin, shell access to a host not running
MySql) cannot create a dump. I may be able to get data out of that
For one, I had misread phpinfo - the fileinfo extension had not been loaded. Two, on a
shared host, loading an extension required creating a ../.php/5.6/phprc file that
included "extension=fileinfo.so". This, too, was learned.
___
TYPO3-english
I have managed to install/move a 6.2.30 site to a DreamHost staging site. After
working through as many of the Install issues as possible I end up with a blank
front end. I've set displayErrors = 1; set to Development mode; added a phprc
file with max_execution_time=240; but still have the
VM installed; directories created, files uploaded.
After loading an archive copy of the database and working through a large set of permission errors and database issues I can get to a List view with File Storage, fileadmin having what appear to be acceptable properties.
Site appears as
I'm going to wait until I can get at the database. Turns out the db is stuck
in some level of v4 and cannot be exported by phpmyadmin or dumped from the
command line. The host will, presumably, create a v4 dump and send it to me.
We'll see...
___
The remote host throws an error when attempting to use phpyadmin to export the
site's db. In an effort to poke at the problem I changed the db password at the
host and applied the same password in
../public/typo3conf/LocalConfiguration.php. This, however, fails! I get the
OOPS message. Any
The src file is above ../public. ../public includes the symlinks.
The installation is highly suspect. The site became inaccessible when the host
did an unannounced PHP upgrade in March. I was the only technically literate
person available to deal with the situation and I was totally
Thanks immensely.
There are two instances of ../fileadmin with largely identical contents:
../public/fileadmin & ../public/typo62/fileadmin. My guess is that the
../typo62/fileadmin can go. Good guess?
___
TYPO3-english mailing list
I'd also like to exclude/trash, if possible, these:
/public/typo62/fileadmin/_migrated
/public/typo62/fileadmin/_temp_
___
TYPO3-english mailing list
TYPO3-english@lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
We're considering moving our current 6.2 site to a new host. The site has
recently been migrated from 4.4 to 6.2. For a guesstimate of the size of the
move I created a tarball of the site - it came in at 1.3GB. This, I know, is
way too big for the current content of the site. I don't want to
Thanks to all who have replied.
I've since learned quite a bit. The fundamental problem I was having related to MySQL's
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION". I
learned from a bug report from 2006 that strict mode caused problems. So removing
It may be possible to import the database if there is a method to deal with a blob that contains a serialized array that contains unescaped text. For example, the array that begins
A remote host has a site using version 4.4.15. As a consultant I want to create
a sandbox away from the remote host. Downloads of phpmyadmin dumps of the
database have been unsuccessful (character set conflicts, unescaped text
halting import). Shell cannot access the database.
The
15 matches
Mail list logo
