I am seeking for a way to move my existing webSPELL userbase into a joomla one.
Is there any way to do this ? Maybe just with a simple sql script ? I only would like the users, mail and passwords to be moved, the rest won't matter.
Thanks !
This is a CLI script for importing users. You can modify the script for situaiton.
https://github.com/elinw/AddUsersFromTable
Related
So for backing up any/all my WordPress sites i use a tool called "BACKUP BUDDY" and its
a great tool and all but lately its been really buggy and today finally it went kaboom!
Usually my workflow is that i develop the site on my local machine using WAMP/MAMP.
when done and ready for testing i use the tool, move it to my personal test server to test and when happy and work is approved, i move to the real server.
Since my tool stopped working(uploads half the content) i decided to just do it manually by installing Wordpress first on the real webserver(done), Applying my theme(done),
then exporting the database sql from the local server(done), and thereafter importing it to the real server(done) and the 2xs that ive done it the site comes up blank.(outcome equals major fail!)
im assuming that something has to be changed/done in order for it to work but not sure what.
unlike a normal DB where i can talk to the info as normal, since WP is a CMS im assuming that it ties the info to the domain but again, i dont know how it 100% works...
Any ideas as to what im doing wrong? because as of now, if i cant do it like this, id have to manually create ALL the pages. Plus, if i was going to then move it from my real test server to final real destination then id have to manually redo it all again...
Thanks in advanced.
you aren't doing anything wrong. It sounds like your particular workflow could be as follows.
Upload the contents of the site via FTP
Create & Import the database via PHPMyAdmin, changing any info in wp-config.php
Define the site url, in wp-config.php [See below]
Use a tool to find & replace any hard-coded site-urls that wordpress loves to use. [See below]
Example code:
Define site urls
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
Find replace tool
Replace
http://localhost/
with
http://www.your-new-site.com/
That should be it. It's live!
You can export it using phpMyAdmin and then use bigdump to import it. download bigdump from here and make sure you read the first note about the exporting process, found here
http://www.ozerov.de/bigdump/usage/
here is a bash script you can use to automate this entire process for you: https://github.com/jplew/SyncDB
I am developing multi-sites with drupal.
I have to take care of 10 sites and they need single login
I supposed I need to create separate user database to support that
feature.
i.e 10 sites, 10 database and +1 user database.
Where should I look and modify? User Module? Which lines?
Normally database settings are in settings.php file .
I had export the database and make and working user-database already.
Please kindly try to explain in details thanks.
I don't know the full details of your situation but it sounds like you might benefit from one database with prefixed tables and a shared user table.
See
http://thedrupalblog.com/setting-multi-site-drupal-6-installation-shared-databases-and-single-sign and http://drupal.org/node/201673 (bit outdated but may still be helpful)
I have a Bugzilla installation and I would like to clean the bugs, projects, components etc from it to start clean. But I would like to keep the users and other settings. How would I best do this so I don't fragment the installation?
The fastest way, for me, was simply to delete all the tables in the database. Most of the settings are kept in other places. Then run ./check-setup.pl script again and it will create the tables again. You could save the users table and add the users back once the script is done to avoid having to create all of the users again if you have many.
I am working on a Ruby on Rails 3 web application using sqlite3. I have been testing my application on-the-fly creating and destroying things in the Database, sometimes through the new and edit actions and sometimes through the Rails console.
I am interested in emptying my Database totally and having only the empty tables left. How can I achieve this? I am working with a team so I am interested in two answers:
1) How do I empty the Database only by me?
2) How can I (if possible empty) it by the others (some of which are not using sqlite3 but MySql)? (we are all working on an the same project through a SVN repository)
To reset your database, you can run:
rake db:schema:load
Which will recreate your database from your schema.rb file (maintained by your migrations). This will additionally protect you from migrations that may later fail due to code changes.
Your dev database should be distinct to your environment - if you need certain data, add it to your seed.rb file. Don't share a dev database, as you'll quickly get into situations where other changes make your version incompatible.
Download sqlitebrower here http://sqlitebrowser.org/
Install it, run it, click open database (top left) to locationOfYourRailsApp/db/development.sqlite3
Then switch to Browse data tab, there you can delete or add data.
I found that by deleting the deployment.sqlite3 file from the db folder and inserting the command rake db:migrate in the command line, it solves the problem for all of my team working on sqlite3.
As far as I know there is no USER GRANT management in sqlite so it is difficult to control access.
You only can protect the database by file access.
If you want to use an empty database for test purpose.
Generate it once and copy the file somewhere.
and use a copy of this file just before testing.
I have created a database system for a cms for a news website. I want to have only 4 roles in my db system : Admin, Author, Editor and Guest ( who only read the web pages). But there are some pre-defined roles in every db system like sys and db_owner and… and they are not removable but I want the only 4 roles I mentioned above. How can I aim this goal? thanks
ah, you cannot!
Also I do not think you will need to tweak the database system. Rather, architect a good solution for your application/frontend/website.
as far as i am aware, you can't modify those roles (besides adding logins to them). instead of working around them, you could try using them, it might make life a little bit easier.