CMS Made Simple Forums

Not knowing anything about MySQL or php, I think this will be an easy answer. I have searched everywhere, but can't find the answer to this specific question:

Mac OS10.4.8  MAMP 1.7.1  CMSMS 1.2.2

I have developed the site locally  http://localhost:8888/cmsmadesimple/

I have ftp'd this entire local cmsmadesimple directory to my server, set permission correctly, and changed the config.php file to new paths

I have set up a clean database using myPHPadmin on the server.

When I "view site" on server it has none of my content, templates, or stylesheets applied, even though they were FTP'd up. I then tried to re-import" the using theme manager - Still doesn't reflect content.
I THINK I need to Dump my local database and import/upload it to my server.?

Questions:
Where does my database exist on my local machine?
MySqlDump is asking for my "Path to mysql binaries:"  I don't know what to put in ( /Applications/Mamp/db/mysql)? leave it blank? Everthing I try gives my the "file too small or missing" error, which I've tried to figure out from the forums unsuccessfully.

This is probably very easy - I just want my server version to look and act like my local version so that my client can start inputting content.

Thank you in advance

Cheri

If you have PHPMyAdmin on the local machine, you can use it to export the database, then import it on the server.

Nullig

Yes, I have PHPMyAdmin on both local and server.  I have read the documentation, and still cannot find where it saves the file.

1. I select the database in the left column; Then click Export from the tabs across the top.

2. What do I select in the Export Column?  (I've selected the SQL radio button)

3. I don't know what is going on in the entire right column, so I have left those settings alone (default).

4. I click "Save as File"
The file name template is _ _ DB_ _
Compression is none.

5. I click GO

...and nothing appears to happen.

Where is the file?  (and should I be naming it something?) I never get a chance to set a path.

Thank you

The instructions I usually give to clients...

Full Backup With PHPMyAdmin

- In the Export box, usually all the tables are pre-selected, but, just in case they aren't, click on the "Select All" link. This will select all of the tables in the database.

- Just below that, make sure the SQL radio button is selected.

- In the "SQL options" box make sure the "Structure" box has a checkmark.

- In the "Structure" box make sure that the following have checkmarks:

Add DROP TABLE / DROP VIEW
Add IF NOT EXISTS
Add AUTO_INCREMENT value
Enclose table and field names with backquotes

- In the "SQL options" box make sure the "Data" box has a checkmark.

- In the "Data" box make sure that the following have checkmarks:

Complete inserts
Extended inserts
Use hexadecimal for binary fields

- Also, in the "Data" box, ensure the "Export type" is set to INSERT.

- At the bottom, make sure that the "Save as file" box is checked.

- Click on the "Go" button.

- This will create a "sql" file - Select the "Save to Disk" option and click on the "OK" button.

- Find the file you just saved in your usual "downloads" directory and rename it to something like FullBackup-yyyymmdd.sql - I usually format the date like 20080110 for sorting purposes.

Nullig

Thank you - It was in the downloads folder, as you said...

Now, after I export, do I just go to PHPMyAdmin on my server, select the database I am going to populate, and import?

AND, the databases have 2 different names - will that be a problem?
(I created the local install of CMSMS first, using the suggested database name, cms. I created a new database on the server, and it requires my hosting username_ as the beginning of all database names.)

Thank you for the info -

Yes, you can use that file to import to your server using PHPMyAdmin.
The database name doesn't matter, you're only importing the tables.

Nullig

Hello,

cammac2 wrote: CMSMS 1.2.2

You are at risk if you run this old unsupported version on the wild Internet.
You should first upgrade locally to latest official stable, then move to the Internet.

Pierre M.