kongondo

I suppose you want to do this for SEO reasons, but like Diogo said, changing parents like that is not good practice...

Btw, this was a double post and a similar response was posted by Adrian http://processwire.com/talk/topic/4503-getting-most-recent-pages/

Create and delete branches: https://github.com/blog/1377-create-and-delete-branches E.g. "master" and "dev" are the 2 branches of PW: https://github.com/ryancramerdesign/ProcessWire/branches Stuff others may find useful Branches Commit branch and tag labels: https://help.github.com/articles/commit-branch-and-tag-labels Setting the default branch: https://help.github.com/articles/setting-the-default-branch Other FYIs: How do I work with branches in GitHub for Windows? https://help.github.com/articles/how-do-i-work-with-branches-in-github-for-windows Fork A Repo: https://help.github.com/articles/fork-a-repo Creating Releases: https://help.github.com/articles/creating-releases What are the differences between SVN and Git?: https://help.github.com/articles/what-are-the-differences-between-svn-and-git

Mary, I suppose the questions are: 1. Why do you need thousands of templates? Are the baby sites structurally different (e.g. one has title and headline field, the other only has title, or different markup, etc) and/or are they aesthetically different (CSS)? 2. Will the baby sites each have more than 1 template? Max number of templates? In the end, you do not need each to have unique templates. You can have a base template and pull in .inc or .tpl files via the API to populate the unique portions of the baby sites in the frontend. Soma proposed a wonderful "template delegation" approach that would fit your project nicely, I think. Have a read here. http://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/. There's other approaches there as well. So, instead of ending up with thousands of templates, you could end up with thousands of template file includes. Even then, I should think you can still cut down on the numbers depending on the uniqueness of the baby sites. It just needs careful planning/mulling over. Having said that, I don't think having thousands of templates will have any performance issues in the backend. I could be wrong on this one since I have never tried it though . You'd probably have to organise them in such a way you could easily edit them. You could use tags to group them in the backend. You could even go fancy and create a simple module that would list your templates in a table, maybe with pagination + search function to filter the list, + a click to edit a template (add fields, etc). The link could take you to the PW template edit screen or could open a modal to edit the template. This would be sort of extending the PW template backend view. We can help you get there if you want to take this route. Just my 2cts, there will be other thoughts am sure...

You can already use one image multiple times across different pages over and over . I am assuming you mean inserting an image in a page using a rich text editor. if, on the other hand, you mean several pages sharing the same image in their image fields by referencing only one uploaded image, then ignore my response As for an assets manager, that has come up a lot in the forums..., btw...

Hi bodhic. Welcome to PW and the forums! We seem to be attracting more and more people who are also familiar with MODX (me being one of them ). As you've stated, there are various ways you can accomplish this. It all depends on how easy you want it to be, either for yourself or your client and maybe also, just a matter of preference. One way to go is with those fields in one page, though, I don't think I would go for that. 8 or more content areas may just be too much on one page . Again, it depends on your needs/preferences. Another approach is to have those "content areas" be child pages themselves. What I mean is this. Create what you want to go into content areas as pages. Using the rich PW API you can easily pull them all in in one template file to output them on your website to display their respective contents in your 8 or more content areas (maybe divs). I hope this makes sense. For other needs (probably not what you are after), there are special fields called Repeaters (like MODX MIGX). These are useful when you want to output content that repeats. If you haven't seen it, checkout this thread. It is an attempt to guide those with a MODX background meeting PW for the first time Feel free to ask questions if any of this doesn't make sense. Edit: Just seen PWired's post also links to the above post. His link also has some other wonderful resources

It is not possible to just fork part of a repo (in this case PW) - not that I know of. You lose nothing btw by forking "the full PW dev repo" as Github offers unlimited repos . So, yes. Please, fork the dev branch, make your changes and submit a pull request for those changed files. See this link for step-by-step instructions: https://help.github.com/articles/creating-a-pull-request Edit: OK, there seems to be a way to partially fork a repo though I am not sure it is worth the effort. There is something called "sparse checkout" in Git. There's tonnes of topics on SO and other places about this. I would just fork the whole branch. One advantage with that is that it allows you to easily test your changes in the whole system to see if they break anything...

Yep... https://help.github.com/articles/creating-a-pull-request

Aah. Sounds nice. Mine doesn't really do the access management per se, at least not in that sense. It just simplifies the task of creating users, assigning roles, etc and sort of provides a directory of users in one nice interface, that can be applied to different scenarios.

That's make two of us then...though mine is a fun project, a learning platform... I'm sure yours will be much better

<aside>I have one main PW install for testing stuff. I have have two wire folders. named "stable-wire" and "wire". The former has, well, the stable version of PW and the one for my daily use has the "dev" version. If I need to test something in the stable version, I temporarily rename the folders. "stable-wire" becomes "wire" and "wire" becomes "dev-wire". I used to have two different installs but thought that didn't make sense since PW core is in the wire folder. Am doing this the "wrong" way? </aside> Apologies for temporarily hijacking this thread

Stop it all of you! You are confusing me! If you have an avatar, stick to it! hehe

Welcome to the forums Jonathan Dart Without guest role your site is not viewable I believe Maybe if you could explain what exactly you are trying to accomplish? If you don't create any other users, i.e. leave only the defaults (superuser [you] and guest [can only view]), then you have nothing to worry about. Maybe am not getting you Edit: I knew I was not getting you.having read Apeisa's post below...I am kinda slow that way

I'm totally confused by this discussion. What do modules have to do with head.inc? Edit: OK, I have read Wanze's post and it is beginning to make sense. This is not an everyday case for modules but a situation where interaction with template files is required (right?)...I just needed to clarify lest new comers to modules got confused

Awesome first post Karl! Welcome to PW

Shouldn't this be Europe/Warsaw by the way?

Joe, Nice to know it is resolved...

If you want to read more about what Soma is saying (and have the time )+ some of the thinking behind it, check out this long thread, maybe from post #19 http://processwire.com/talk/topic/3217-field-set-to-unique-in-table/

danysrour, Welcome to PW forums! In addition to above responses, the following threads may be of help. ProcessWire on Windows7/2008 Server with IIS WebServer http://processwire.com/talk/topic/268-processwire-on-windows72008-server-with-iis-webserver/ ISAPI_REWRITE 3 on IIS http://processwire.com/talk/topic/766-isapi-rewrite-3-on-iis/ Mircosoft IIS and Processwire http://processwire.com/talk/topic/3558-mircosoft-iis-and-processwire/ ProcessWire on LiteSpeed Web Server? (See Ryan's post) http://processwire.com/talk/topic/1212-processwire-on-litespeed-web-server/ Can't reach admin page http://processwire.com/talk/topic/1962-cant-reach-admin-page/

Thanks all! @onjegolders, Good ideas, thanks for the suggestions, I'll look into them. music = Fourplay - "Pineapple Getaway"

Strange....well it seems definitely a server configuration issue. Confirm your PHP and MySQL versions. I'd also suggest testing with some low size image (just trying to rule out stuff here) of different types - jpg, png, gif... Btw, is that TinyMCE you are using or CKEditor?

OK, but have you actually checked if anything is written in errors.txt? Could you confirm whether it is one image causing issues or you have tested with different images?

Hi Joe, Welcome to PW and the forums. Did you test PW on a local install? (WAMP, XAMPP, etc). Did it work then? Seems maybe some of your files were not transferred to the server? You can manually create the errors.txt file and see what PW writes to it. Do not post your phpinfo publicly. You can PM it to Teppo to have a look. PHP version? MySQL version? Did you try with other images? Same results?

Hi blickwerker, Welcome to the forums. I have no direct answer to your question but I found a similar question here. The answer was not definitive. Let's wait and see what Ryan says

I would say both if you can. Things can easily go astray in the forums. If you file an issue in Github it is easy to remember it and track its progress. In the Github issue, you can also make reference to your post, for posterity, etc.