Closed (duplicate)
Project:
Deploy - Content Staging
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Feb 2010 at 23:42 UTC
Updated:
12 Jun 2010 at 14:11 UTC
Jump to comment: Most recent
Comments
Comment #1
mlncn commentedIs there a 'but' coming in this? After all those success messages, why do you say it didn't work ;-)
Looked at admin/content/node and filtered by Page on the receiving site to double-check?
Comment #2
pcas00 commentedThere were a couple of module issues that I had to fix and it appears to be working.
Comment #3
Anonymous (not verified) commentedI'm experiencing the same problem basically: Everything is set up according to documentation and deployment finishes with a "Succesful" message, also logs accordingly. But the nodes never end up on the live server, neither new nodes nor updated nodes. I'm kinda lost. :(
pcas00, can you elaborate what modules issues you ended up haveing to fix to make it work?
Comment #4
apotek commentedWe had the same issue, but with deploying a cck type and with deploying taxonomy.
Everything on the sending server made it look like all was working well. But none of the deployed content could be found on the receiving server.
Our fix was to enable clean urls on the receiving server.
The deploy module appears to be relying on some non-Drupal API or request handling... perhaps this is a fault of the services API? In a well-built module, it should be utterly inconsequential if a user has clean urls enabled or not.
Comment #5
apotek commentedI'll bet this turns out to be a duplicate of http://drupal.org/node/526936
Unfortunately, it looks like the Services module needs a fix for its request handling so it doesn't rely solely on clean urls.
Comment #6
giorgio79 commentedyep it does look like a dupe of #526936: Find best way to proceeding with 6.x-1.x