adding Zariz to an existing site

[benjf]

I am attempting to add Zariz to my existing Drupal site. After installing zariz and zariz_ui, I assume my next step is to create a branch, so I added a 'live' branch node. Now, I get a 'redirect loop' error for all pages outside of /admin/* and the url is http://mysite.com/live

I started over with a clean db dump from the existing site a couple times, but I'm stumped. Any tips or ideas on how I might proceed?

more details:

• OG is new to the site, so Article is the only 'group content' type, after installing Zariz
• I don't have any existing Article content
• all Zariz modules and dependencies are the -dev version, except Replicate

Thanks a ton, Zariz looks really amazing!

PS: assuming I get past this, can I have my 'live' branch served without a url prefix?

[amitaibu]

Hi @benjf :)
Does it work ok on a clean installation?

[benjf]

Hello again,

I finally found some time to test this a bit more. I installed a new site, with the Standard profile, then used Devel Generate to create a bunch of Article and Basic Page content. Next, I enabled the Zariz modules and dependencies, then created a new Branch ('live').

At this point, it seems like Zariz is working for new content (Articles are the only 'group content' at this point), but I cannot view or edit any of my existing nodes. When trying to view either type of content, I am redirected to the live branch home page. When trying to edit a Basic Page, I am also redirected to the live branch home page; trying to edit an Article, I get the following error:

Thanks for any ideas you might have!
-Benj

[amitaibu]

then used Devel Generate to create a bunch of Article and Basic Page content

Devel is probably not populating the group reference.
Instead of devel, you can enable zariz_example and migrate-ui, and migrate the demo content.

[benjf]

This is an attempt to use Zariz on a site with existing content, so I used devel generate before enabling the Zariz module and dependencies. The current behavior makes sense for Articles, since the old content won't have a group ref. I was curious how Basic Page would be handled, since it is not a 'group content' type, but it seems like everything should be group content for Zariz to work.

I will try creating a custom module to add the branch field to all content types, and then assign the live branch. I think this will fix the problem.

Q: Is it possible to have my live branch content displayed without the '/live' prefix in the URL path?

thank you, I'll update this after more testing (unless there's a better place for it)
-Benj

[amitaibu]

you would probably need to do some drush/migrate work to get Zariz in place. If you want I can offer for you to send me privately the code/ db and I'll give you some guidance.

Q: Is it possible to have my live branch content displayed without the '/live' prefix in the URL path?

I've started some work on it, but haven't finished yet. Should be possible I guess :)

[benjf]

Thank you!

This is my initial attempt, which is not working yet: https://github.com/benjf/zarizify

[amitaibu]

I would have it as a drush script, which runs on batches of nodes. Basically the idea would be to reference the node to master branch via field_branch.

[amitaibu]

btw, how big is the site you try to add it to?

[benjf]

I like the idea of a drush script vs. the module I started, thanks for that.

I'm currently trying to set this up on a dev site with existing content as a proof of concept, and to get my head around how it all works. So I'm using a very basic Drupal install with 5-10 nodes. The end goal would be to use this on our corporate Drupal site, which has ~1000 nodes.

[amitaibu]

@benjf If there's budget for this, maybe Gizra could help you with the migrate.

[benjf]

That would be great, I'll see what I can do (aka, talk to my boss).

[amitaibu]

great, let me know :)