shogun

What about site/assets/sessions? Those seem to create permissions problems when moving to a server. Are these needed? or are these local to the current copy of the site.

I need to copy a local site to a testing site, but what's the process to do this without having to re-do the CMS portion? I need to update the database username, password, etc. and make sure all CMS updates are the same.

What's your best process with process wire and git. What files do you include (and/or exclude) in git? to make sure you still have all your code backed up in git without having too much unnecessary inflation.

Excellent!

How do you create a single field that is global across all pages and templates so that when its content is updated, it's updated every it exists on the website?

I want to start getting process wire into our workflow. (Someone recommended this to me and I absolutely fell in love with this. It's just what I needed. We build completely custom "static" sites from scratch.) I'm just wondering what's the best workflow. I'm thinking of 2 methods: 1. (Build site first and then integrate processwire) We build a site using all our compilers -> then setup processwire, and start copying each page to the template directory, then mapping templates/pages and fields. I'm worried in this case, will I either misconfigure mapping pages/templates to the copied over pages or there will be some conflict between a page copied to the directory and then mapped in the admin. (also curious about this since we already have a bunch of sites I'd love to map processwire's cms to) 2. (Setup processwire first and then custom code each page) We just setup processwire from the start, create the template, page, fields for a page and then open it up and custom code into the page created by processwire... Just concerned of anything getting in the way of our initial buildout with our gulp and sass precompilers. Any thoughts?

Also would be cool if it allowed you to choose multiple images from the page so you can create a gallery from the stored global images.

I got it working. It's cool. The only thing I noticed after installing, creating the default photo page, adding my photos and then creating the field and adding that field to a page. The first time you arrive on a page that uses the new field, I got this error. It went away once I attached an image from the photos page, but I assume it would be more user friendly if there wasn't an error on the initial load before a

This is exactly what I was looking for. Sorry for the dumb question.... How do I actually install this into processwire for it to recognize? and what would be the exact name of the module?

I deleted the blog profile I was playing with and setup the blank profile instead. It's outputting a single instance now as it should with: <?php echo $page->featured_image->url; ?> Maybe the default blog profile had some duplication going on at the top of the blog template that I wasn't aware of, (although I didn't see anything that indicated the code should repeat). Either way, all good now! Thank you! I'll most likely stick with the blank template anyway.

(Sorry for the dumb question. I'm just getting started.) I literally have an image field called "featured_image" with a limit of 1 image. Every time I try to output this image, it renders twice. It's driving me nuts. I don't get why. <?php echo page()->featured_image; ?> the page outputs: zara.png zara.png