rick

I have not seen an htaccess file with a version number on it. The install procedure should have renamed the htaccess.txt to .htaccess if your permissions were set correctly. Is your document root defined as reidsengland ? Or is the document root reid ? If the docroot is reid, and you placed the PW files in the reidsengland sub folder, then the rewritebase should be /reidsengland/. You have probably already seen this, but I'm posting it for others too. Troubleshooting

Hi @eutervogel, This is a great site. Nice work! The only observation is the media query breakpoints need tweaking. As the viewport narrows, the logocontainer div, catsinner div, and videoholder div contents do not scale well. For example, at 960px. Otherwise, this is an impressive site. Well done. PS. Welcome to the forum!

Hi @SamC, Yes, my /home/policy page uses the policy template. The /home/policy/privacy and /home/policy/tos pages also use the policy template from the allowed template for children setting. I just redirect /home/policy page to /home/policy/privacy page to prevent access or 404. As I said, there is probably a more ProcessWire-esque way to do it, but I don't know what that would be.

If it is a new install, then the user salt (site/config.php) will be different, which affects the passwords.

I am sure there are idiosyncrasies with certain hosting environments, but I have not run across anything outside what the general upgrade instructions dictate. There is also a profile export module with instructions in this thread that I found very helpful.

Also, your figure images in the photos section aren't aligned in Opera, Chrome, and Firefox... It might seem as though we're picking on your site, but in fact, quite the opposite. I really like this site and how you put it together so I hope you don't mind the help.

I was referring to google moving toward the https preference; a secure site is preferable to it's non-secure counterpart. Also, the www prefix became redundant a few years back and isn't necessary any longer. The dns record accounts for those users who still use it. You have two separate web sites with two separate domains, or is this what you were referring to with www.domain.com pointing to one site, while domain.com points to the other? Depending on your hosting provider, there are configuration files specific to a domain located somewhere. I run unbuntu on my laptop (LAMP) and debian (LAMP) on my production server. Apache is using sites-available/sites-enabled structure to hold the virtual config files. My non-secure (http) virtual config looks at requests on port 80 (non SSL) and redirects to https. This is where I was getting confused. You mention both protocols (http and https) point to the same content, but you also mention how to modify the code used for both sites. Is it two different sites serving the same content? Having separate registrars and separate hosting providers is only a management issue for you (or whomever is responsible) by having to log in to different accounts to manage the information. Purely as an option, you could eventually consolidate your domains under one registrar, and even place all the domains on one hosting account.

That I don't know. I don't use a multi-language setup.

That turns off output formatting, as described here.

Also, if I (user:Rick) am getting two emails, the first is my confirmation, and the second is for user:Xonox confirmation, then I either entered my own email both times, or your code is not reading the email field value with the second form submission. Are you using the current user anywhere to retrieve any information, such as the email address?

Ok, on my second cup of coffee now. So the desired resulting structure is like so: /agenda/ /get-a-cup-of-coffee/ /rick /xonox $p = new Page(); $p->of(false); $p->template = 'reservation'; $p->parent = wire('pages')->get('/agenda/' . $sanitizer->text($input->post->page_target) . '/'); $p->name = microtime(); $p->title = $form['name']; $p->save();

Hi @Xonox, A couple of things stand out at first glance. The naming convention is confusing to me. Specifically, the use of 'name'. For example, 'name' is a property of the input form, and any other form element, such as input fields, and it's value is what gets submitted with the form. Could the $input->post->name field be firstname, or username, or document name, or something uniquely identifying that specific field? Then there is the use of the '$form' variable. I understand what you are doing, but it is very confusing to read. This could be $inputForm, or whatever you think is more meaningful. Last thing is the 'parent' property of your new page. If the $input->post->page_target value turns out not to be valid, then the save function would fail. Why is a 'known' value being passed through input processing? Or is this a select field with only known pages as valid options? Sorry for my confusion. It's my first cup of coffee.

Maybe I am missing something, which is quite possibly the case. So please educate me. There are two protocols, http and https, for a single domain, but including the extraneous www, gives four combinations. As previously mentioned, www can be defined at the Address record level (or CNAME depending on provider) at your hosting provider. This in effect allows users to type or link to www.yourdomain.com and yourdomain.com resulting in the same hosting server doc root destination. So that leaves the two protocols remaining. Are you serving content specific to a non secure site that is not available through the secure site? If there is no specific content unique to one site, then you can use https://yourdomain.com (better google results), and also set the ProcessWire templates to https only (Although that last part is optional). In my non-secure site conf file, I redirect non-secure requests to the secure site by the following: <VirtualHost x.x.x.x:80> ServerName domain.com Redirect permanent / https://domain.com/ </VirtualHost> This is my exact setup, and using the ProcessWire generated htaccess file. Google's page speed reports, "In our test, your server responded in 0.28 seconds." There were no re-direct incidents, and visitors can access my secure site using any of the four combinations. Like I said, if I am missing something, then please let me know. I'm always open to learning something new.

The site is fantastic! It loads very fast for me too. Only suggestion I'll make is to quicken the menu animations slightly. It just seems a little sluggish compared to the speed of the rest of the site.

Just a guess, but did you enable the permissions for that (those) field(s) in the Module > Site > User Profile > Settings page?

Ok, I haven't found anything that relates to php 5.4 being a problem with 3.x. Although php 7 would be better. If you can get them to upgrade to 7 then do so. A 500 error is 99.99% due to the server not liking something in your htaccess file. Something was initially configured incorrectly with your server, or one or more files (htaccess) were corrupted during upload, or both. Regardless whether they upgrade to 7, try this: Delete the current ProcessWire install, including all folders and files. Drop the database and re-create a blank database (utf8mb4_general_ci collation, located toward the bottom of the list). Note the database name and user:password for use later during installation. FTP the ProcessWire files to your public_html folder. Either FTP the zip and extract (keep directory structure) to your public_html folder, or FTP the folders and files from your local machine. Don't use the hosting control panel's upload feature -- use only FTP. Run the installation again. If you get any error, stop and post back here. Note: If you extract the zip file you may see them in a ProcessWire-master folder in the public_html folder. If you do, simply move the files and folders up one level, then you can remove the ProcessWire-master folder.

Can you have bluehost upgrade php to 7.x? Also, what mysql version is running?

Hi @Chamche, Installing ProcessWire is really straight-forward and easy to do. Ryan has done a tremendous job ensuring that. There just seems to be a minor glitch in the procedure you used to set this up. But we'll help you get this sorted out. The problem now is, You deleted the original .htaccess file, Renamed the htaccess.txt file to .htaccess, Attempted to install ProcessWire and got the same error, Restored the original .htaccess over the renamed (ProcessWire) .htaccess file. Is that correct? In your other thread, you said the server was running php 5.3. Did you have bluehost upgrade to php 7? We are kind of lost here with where you currently are with the server config and ProcessWire installation. So, let's start from the beginning. What apache version is running? What php version is running? What is the ProcessWire version you are installing? Is bluehost running cpanel? (I'm not familiar with it so I have to ask) What is the content of the error.log file? If there are still issues after answering these questions, would you be willing to provide your login credentials (via Private Message) so that we can take a look? Note: You should change your login credentials after the installation is complete so that only you have access to your hosting account. One last thing. It is never a good idea to be configuring a server when you are tired (I know from experience. LOL). Get some rest and come back to this later. We'll be here to help you out.

Try this reference... Troubleshooting Guide What is your Apache version?

Hi @Chamche, and welcome to the forum! The permissions look right. I see that you registered your domain a few days ago, so dns has had time to propogate. Are there any error entries in your log files? You can copy a test index.html file to the public_html folder to see if it displays correctly. It only need contain some generic text. If it does not display, then it would indicate an error with the server setup. If it does display correctly, then it would indicate possible corrupted ProcessWire files when you copied them to the server. If so, then you need to delete all of those files (not overwrite them) and re-upload them. Preferably using ftp. Again, welcome to the forum.

Hi @desbest, There are any number of topics and modules in the forum discussing this, google: site:processwire.com/talk/ "frontend login" for a comprehensive list. If you can explain what it is you want to accomplish with your project, I'm sure many will offer up suggestions about which way is most efficient for your needs. Let us know if you have any questions.

Does this not work? if( strtolower( $attach_file->title ) == 'yes' ) { // do whatever }

@Robin S Just an FYI. I followed your procedures to export my local dev profile and install it to my live server. Everything went without a hitch. I owe you a coffee, a beer, and a pizza!

My 16.04 is /var/www/ The 14.04 ran without a hitch. When I upgraded to 16 I had to change the following... Apache is 2.4.18 so the htaccess will need to be modified. Comments are in the file. There was also something specific to php 7, like mycrypt, exif, etc. not being installed. I don't recall offhand. I'll check and get back to you.

I run let's encrypt too, without any errors, so I don't believe it is a problem with that addition. So your domain is at a registrar and your hosting is with a different provider? Just look to your registrar for the dns change. It doesn't have anything to do with your hosting provider, other than getting the correct IP address.