Drupal 6 nodes not appearing in content list after migration - mysql

I've copied a Drupal installation from the production server to a development site to do some additional work. It all seems to be set up OK, other than the fact that nodes of one particular content type do not appear in the content list or at their node/nid or aliased urls, I just get 'page not found'.
To migrate, I copied the database directly, moved over the files and updated settings.php. As I mentioned, the rest of the site works fine, its just missing lots of nodes which ARE in the database, but not picked up by Drupal, even after refreshing the cache, running cron.
Any ideas appreciated!
Cheers

Are all your nodes missing? Were you using clean urls on your production server? If so, are these enabled on your development site?

Related

How to get file contents of old site on drupal?

We have a site running to drupal and migrated it to Squarespace. I have to retrieve some pages of drupal site but I can no longer view the site. Do you know any way to get the old content of website on drupal? Please know that we still have access to the drupal box. Any suggestions will be a big help.
Easiest way would be to make the old Drupal site available again through the browser running on a different domain like old.example.com, login into the admin panel and start copy/pasting content.
If you know your way around your computer, know the IP address the old server is running on you could for the time being change the host file of your machine to send requests for your site to the old server and get access to the site that way.
Migrating content by automating the process is also an option, but it is not only time consuming, it requires in depth knowledge of both platforms so is mostly a very expensive solution if you are not able to do this yourself.
But if I read your question, I think the first option is the easiest option. Get a hold of the technical person/party of the server the site is running on and get them to make the site accessible on a different domain.

Unwanted code being inserted into pages

Some of our ColdFusion sites are having the words "coupon" inserted into their footer with a link to another site. Is there anything I can do to prevent this? Is there any software I can run to help detect any vulnerabilities? It doesn't seem to be SQL injection as the databases seem fine and nothing unusual is showing up in the logs.
There are several variations of attacks that produce this sort of result (appending a link to some malicious or nefarious site). For example, this one (Script Injection) uses the latency between a file upload and checking to insert executable code on your server.
Other attack vectors include FTP (which is why you should not use it), or other file transfer protocols. In your case the infected machine may not be the server. It could be a client machine with access to the server - a developer who has set up FTP to the server for example.
Let me know if you need formal help - we have a good track record fixing this sort of thing. If you get more clues post them and I'll try to help. I will warn you that if this is a server infectionit is at the root level and is so pervasive your only option is to start with a pristine install and reinstall your code. Bad news I know - sorry :(
We had something similar happen when one of our servers was hit by the hack Charlie Arehart describes here:
http://www.carehart.org/blog/client/index.cfm/2013/1/2/serious_security_threat
Have you had these patches?
Another option that I would recommend is searching your site(s) for any use of the <cffile> tag that isn't expected. I had a customer that somehow got a single file that was a backdoor to their site. It was particularly dangerous because it could upload files to any location on the server as well as execute any SQL command against any datasource on the server. In other words, this single file opened the door to all of the sites and databases that were running on that server.
This backdoor file (which was named vision.cfm) was often used to update footers with links to coupon and spam sites. vision.cfm was only 210 lines of code.
The entire server had to be sanitized after this was discovered.

Migrating Widget Settings in WordPress

I've done a lot of WordPress migrations from one server to another at work and elsewhere, but one strange thing I've never been able to understand is why widget settings never get carried over.
I'll dump the MySQL database, find/replace localhost with the live domain, SSH the database up to the live server, and then ftp the whole WP installation (core and theme, from my local machine), and still the widget settings are wiped out. And sometimes this is also the case with values saved in theme options pages I make in the Dashboard.
What am I missing?
Wordpress stores widget options - and some plugins and themes also store their options - as serialized data, and so you have to be more careful than a full find/replace of the URLs.
Much more comprehensive answer and some other ways to do move databases and retain serialized data: https://wordpress.stackexchange.com/questions/9076/why-is-my-database-import-losing-text-widget-data
To move a wordpress site and to reconvert all serialized data I used this script.
the using is very simple, download the script, change the credential variable to the database inside the php script and run it.
link to download the script:
http://davidcoveney.com/575/php-serialization-fix-for-wordpress-migrations/
work fine.
Don't do it manually!
Dont edit database manually when migrating between different domains!
Use small scripts, like this:
Wordpress-Migrator.php (read description too.)
because SERIALIZED arrays needs to be modified specifically too!!!

Odd Umbraco backend behavior after deployment

I've had this before, but can't seem to replicate the steps I did back then.
I've got an Umbraco 4.5.2. site which is running on port 8084 in a development-environment. All works well.
When I want to publish the website to the production server, the umbraco-backend seems to want to keep using the port 8084 and therefor my backend (starting at login) is really strange. Can't seem to update any content (or anything else for that matter).
Now, I assume, it has something to do with caching of sorts, but what setting to change (or what to delete)?
This is my login-screen (no red border on erronous login)
And this is my back-end (there is content - i can see content in the front-end - just not visible in the content-tree);
This is my back-end on the development machine (did nothing but crude copy and edited the database connectionstring to match my production database).
How do you change the port number? I am assuming you're putting it into the hostname on the root item in umbraco content tree.
Have you tried republishing the entire site to make sure the published links do not contain the port number?

Drupal 6: using too many Views module causing site to go down cos of too many mysql connection

I have HostGator Baby Shared Plan . I develop Drupal site on. everything was fine at the beginning, then by the time i go further with development, site started ti work really slow. now it is not working at all. giving my sql errors like TOO many connections, etc...
I created so many blocks, pages with View. so it makes my site to so much depend on database. should not I do that? can it be the reason of my site's no working now.
appreciate helps!!!!
Don't use HostGator. If you're looking for something in the same price range, try DreamHost -- they officially support Drupal on their hosting plans.
Ferran's answer is fine once you're done developing, but you shouldn't devlop with cache turned on or else you won't be able to see your own changes.
Yes, Drupal uses a lot of Database. However, you can cache the results of most Views (check the main screen of each view to enable it) and also there's an option to cache the blocks. It all depends in the content of your views and if users are mostly registered or anonymous.
You can also use modules like Boost which saves static html pages so for anoymous visits your database is not touched at all (just the first time, as the page needs to be generated someday...).
You might also want to check the Views filters, not fetching to many rows at a time (for example fetching a week back for the front page).