I am developing a website using Django 1.11 and Django-CMS with python3. Initially I used the default database sqlite3, however, now I want it to migrate to mysql. I have found several solutions online like
Solution 1
Solution 2
However, both did not work. For the first solution I got the following error:
AttributeError: 'Page' object has no attribute '_node_cache'
and for the second solution there was this error:
Could not load contenttypes.ContentType(pk=1): (1062, "Duplicate entry 'cms-placeholder' for key 'django_content_type_app_label_model_76bd3d3b_uniq'"
In both examples, I used a empty database and migrated first.
Any help please?
Django's content types get tricky. Try deleting the content of django_content_type from the database after running migrations, but before loading the fixtures:
python manage.py dbshell
DELETE FROM django_content_type;
If it loads successfully, run migrations again to fill in any missing entries in django_content_type. Good luck!
Related
I'm attempting an upgrade from mediawiki from 1.24.4 to 1.32.0 on a shared hosting platform (Dreamhost). The upgrade appears to be bombing out trying to open the patch-indexes.sql file. Permissions on the file are (-rw-r--r--).
Error message:
Turning off Content Handler DB fields for this part of upgrade.
...have ipb_id field in ipblocks table.
...have ipb_expiry field in ipblocks table.
...already have interwiki table
Updating indexes to 20031107 ...
An error occurred:
Could not open "patch-indexes.sql".
Purging caches...done.
I'm wondering if anyone has solved this problem before.
I had the same problem.
The reason for this was the incomplete database. I had to update from 1.24.4 to 1.31.1 and the rebuild of the database broke on the new server with phpMyAdmin. After I had chosen another software to create the database (e.g. mySQLDumper) it works fine.
Paul
I get errors on build stating 'The System cannot find the file specified' for each of the 3 metadata files 'CSDL, MSDL, SSDL'
Able to generate model from DB fine, connection string fine. Reinstalled the correct connector just fine and MYSQL as a provider appears fine in VS2012.
The 'Metadata Artifact Processing' propery on the model is set to 'Embed in Output Assembly' as instructed.
Out of ideas and hours to keep hunting, would really appreciate a fix here.
This was happening as I had a build script that deleted these metadata files as a result.
Sorry, my bad.
I have a slight problem with a wordpress migration. I've bulk uploaded posts from csv on my local WAMP server as it's faster and then uploaded & imported a SQL dump to the remote server.
In the guid column of the wp_posts table, it contains the url of the post - I presume (might be wrong, please correct if I am) this is the same as the 'permalink' setting when you edit a post - and all of them are http://localhost/post-name/ which is fine for now, I'm happy to work on an SQL query to replace if needed.
I've uploaded the SQL dump and it still shows 'http://localhost/post-name' in the remote server db as expected. However when I search for a post on the frontend, just to make sure it's picking up the posts OK, I was expecting the links to give me a 404 error until I changed the links, but they don't - they point nicely to the http://remoteserver.com/post-name/
Where as it's a nice problem to have as it still works - I was wondering why & do I need to change it? I prefer to not mess with the db if at all possible.
When migrating, you might need to define your wordpress url in wp-config.php, and I recommend find and replacing the database with this tool. It's pretty neat, because it pre-populates your database from your config file. Obviously, you'd replace http://localhost/ with http://www.yoursite.com/
define('WP_HOME','http://example.com');
define('WP_SITEURL','http://example.com');
I have a client who needs to have data imported into drupal from a large spreadsheet. They already had the modules setup and I have the data all in the right tables... so it seems. I have run my own custom scripts to manipulate what was in the spreadsheets and exported / imported it into the drupal databases.
However, when I go to view that type of content in the backend, it shows there are multiple pages of data but displays "No content available." in every page. Here are the tables I imported to:
// for the business listing node type
field_data_field_bd_address_city
field_data_field_bd_address_street
field_data_field_bd_address_zip
field_data_field_bd_business_type
field_data_field_bd_contact_email
field_data_field_bd_contact_name
field_data_field_bd_description
field_data_field_bd_image
field_data_field_bd_listing_type
field_data_field_bd_phone
field_data_field_bd_tags
field_data_field_bd_website
// drupal default tables
node
node_comment_statistics
taxonomy_index
taxonomy_term_data
taxonomy_term_hierarchy
taxonomy_vocabulary
Am I missing any tables that I need to import data into to make connections?
I had this problem before and it took me a while to solve it. This was before anyone had mentioned the feeds module to me so I thought it was my only option.
If you're going to upload straight into your database you need to enter the data into the revisions tables as well. So you would have:
// for the business listing node type
field_data_field_bd_address_city
field_data_field_bd_address_street
field_data_field_bd_address_zip
field_data_field_bd_business_type
field_data_field_bd_contact_email
field_data_field_bd_contact_name
field_data_field_bd_description
field_data_field_bd_image
field_data_field_bd_listing_type
field_data_field_bd_phone
field_data_field_bd_tags
field_data_field_bd_website
And also:
// for the business listing node type
field_revision_field_bd_address_city
field_revision_field_bd_address_street
field_revision_field_bd_address_zip
field_revision_field_bd_business_type
field_revision_field_bd_contact_email
field_revision_field_bd_contact_name
field_revision_field_bd_description
field_revision_field_bd_image
field_revision_field_bd_listing_type
field_revision_field_bd_phone
field_revision_field_bd_tags
field_revision_field_bd_website
The same goes for the node table. This took me a while to work out and worked for me. Typically someone then mentioned the feeds module which would have saved me time but I thought I'd share what worked for me.
Instead of manually importing the data directly into the database and trying to figure out how to satisfy all the relational dependencies to make it work, I would suggest using the Feeds module
If you wish to continue with the manual process, perhaps this ER diagram of the Drupal database will help (keep in mind it is a bit dated and was likely based on earlier versions of Drupal 7).
I figured it out. I had to add data to the node_revision table with status of 1 set to all the nodes and it worked out just fine after that!
First, thanks for your help.
As a noob, I've been happily chugging along this well-known tutorial:
http://ruby.railstutorial.org/chapters/static-pages#top
and I'm caught in a section where I enter
rspec spec/
where I receive 2 errors. The 2 errors are in the format of
PagesController GET 'home' should be
successful
Failure/Error: Unable to find matching line from backtrace
Mysql2::Error:Unknown database 'xyz.rb'
where "home" is the name of the action/page. The xyz.rb is the arbitrary
database name I have listed under the test section in database.yml. I
have already raked the database.
I'm pretty sure my problem has to do with how I'm not going with the
sqlite3 in the tutorial but instead with mysql2. The resources I have
managed to find only give guidance on what to input for the development
section in database.yml, but not for the rest of the sections like
"test". So, my question is, what exactly does this error mean, how to
fix it, and how should I configure my database.yml file? I tried
entering a file I see in my db folder like schema.rb, but this renders
the same error.
Thank you very much for your help.
You have two options:
Set up another sqlite database, as is default with a new rails application, or
Create another MySQL database, the same way you set up your development database, with a different name (such as test) and use that for testing.
Here's my database.yml file from the Rails Tutorial that uses SQLite for all the databases; you should be able to copy the test section if you decide to go with #1 above.