ohthanks

Yep, it completely makes sense to throw the 403, I was thinking through the down sides of just allowing a page named "site" to co-exist with the the default site directory and and it seemed liked it would potentially cause a lot of issues for exactly the reasons you stated. The index.config.php solution seems to have worked great. Thanks guys!

I've been building out a website design that has used "site" as a page name and my install was throwing 403 errors loading the page. I would really prefer to not change the url-slug so I have renamed the site directory and edited the root index.php $siteDir variable to reflect the new site directory location. Seems to work fine, am I missing anything that will cause problems with the install? Is there an easier way to accomplish this? I tried finding the cause of the 403 in the default .htaccess file with no luck. Is proccesswire internally checking to see if the current url matches the $siteDir and throwing the error? Thanks!

After reading a few more threads relating to this it seems like the obvious answer is to just upgrade php versions on my dev and local servers, which has worked. I think having 5.3.3 was the primary source of my issues.

Hellllooo, This week I was deploying a site I have been working on locally on my macbook / lion install to my ubuntu dev server and realized I couldn't login to the admin on the remote server. After spending an evening on it I think I narrowed it down to the fact that the install originated on my stock lion php build (version 5.3.13) that did not have mcrypt installed at the time and I was deploying to a 5.3.3 version on the remote server. The server was throwing "unable to generate hash" errors and I eventually resolved it by having "supportsBlowfish()" on line 220 of /wire/core/Password.php return false as per one of Ryans suggestions in a thread. So, my actual question is, it seems like PW 2.3 hashes are incompatible with earlier versions of php, what is the best practice for developing when you know (or don't know) if you are ending up on a version of php that will be incompatible with the passwords saved in the database? Do you plan to just reset the database passwords once you are setup on the production box or do you use an older version of PW in the event that you know blowfish support won't be available? Or just do what I did and force the install to revert back to a previous hash method? Just curious if anyone has had these issues or your thoughts on it. Thanks!

This is great btw, been rewriting the previous template/view setup I was using to incorporate these changes. The only issue I'm having right now is if I am rendering a partial template with a defined template filename argument TemplateFile.php is still checking & throwing an exception if isn't a file present in the base template folder. For example if I have something like this in a template foreach($packages as $package) { echo $package->render('markup/layouts/package.php', array('layout' => 'package')); } I have to have a empty placeholder /site/templates/package.php file to avoid an exception. I dunno if that is as intended or it is still just checking for the default template file and trying to ensure that's there.

Starting in on a new site tonight and realized I never posted the last site we finished in March. www.la2050.org This was a information frontend site for a campaign to get people submitting proposals for a community funding project. Client was able to edit a ton of the site and never had any issues dealing with the backend. I learned a ton about markup/template organization from the threads here which were unbelievably helpful. Thanks everyone! Thanks Ryan!!!

They were just setup as child pages for each table and then children for each table row with a basic template containing a name field and 4 text fields for each cell. I think I just built the table markup from a basic foreach in the main template file, nothing really fancy.

Hi guys, Finished this one up in Jan, been meaning to post it. Have a few more that are done but need some final polish, I'll post those up soon. www.contactla.com - Pretty simple site, but client was extremely happy with the setup and how easy it is for them to change content/pricing tables. Can't really express how much I enjoy doing sites in processwire. THANK YOU RYAN !!!!!!

This helped a lot, thanks. I consolidated some of my textareas and got plugins etc setup for each of the fields, works exactly like I wanted now.

That makes sense, I looked at editing the main module file but it seemed like it only would apply to newly created instances of the field. Which is fine as along as I know ahead of time. Setting it up as a new site module is great idea, thanks!

Is there a way to edit the config for all of my existing textareas that are using tinymce or do I need to go in and do my changes in each fields' input settings tab? Thanks!

Oh crazy, I will look into the admin data table more now. I would have never thought about doing it that way. I think after coming from EE matrix setups for so long I just try and use repeaters to solve everything. Thanks for the insight. You guys are great.

Hi everyone, Building out my second site on PR right now and ran into setup question I didn't know the best solution to, thought someone might have suggestions. The issue is with a services pricelist page that will have multiple tables of prices with table header and price/detail fields. Setting up a repeater field for each table with the associated itemlist fields (size, price, etc) is a fine solution, but I would ideally like to be able to create new pricelist tables within the page itself and the issue I have is that the tables have different numbers of columns and header titles. For example one pricelist would have say (Filesize, Price) and another has (Size, Print, Proof, Price.) It doesn't seem like there is any way to add/remove the fields associated with a page/repeater from the page editor itself, so what is my best option here for creating fields with variable columns? The only idea I have is to create a repeater with a preset number of content fields in each repeater row that and have the empty columns be left blank. Type Size Price null null type1 11x8.5 $10 null null and then test for value in the template and build the table columns based off that. That doesn't seem like the most elegant solution though, so any ideas would be appreciated. Thanks!