rick

Members
  • Content count

    230
  • Joined

  • Last visited

  • Days Won

    5

rick last won the day on December 26 2015

rick had the most liked content!

Community Reputation

282 Excellent

About rick

  • Rank
    Sr. Member

Contact Methods

  • Website URL
    https://simulatedconcepts.com

Profile Information

  • Gender
    Male
  • Location
    Texas
  • Interests
    Web applications, scotch, hunting, fishing, scotch, graphic design. Did I mention scotch?

Recent Profile Visitors

1,975 profile views
  1. 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.
  2. Can you have bluehost upgrade php to 7.x? Also, what mysql version is running?
  3. 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.
  4. Try this reference... Troubleshooting Guide What is your Apache version?
  5. 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.
  6. 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.
  7. Does this not work? if( strtolower( $attach_file->title ) == 'yes' ) { // do whatever }
  8. @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!
  9. 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.
  10. 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.
  11. @Christophe I had too many redirects at one time in the past which was due to the same thing you are trying to accomplish. With my registrar, the dns option to redirect using a wildcard, such as *.domain.tld (www.domain.tld) to domain.tld covers the initial redirect. Then you can leave the htaccess file to change http to https. This resolved the issue for me.
  12. Do that all the time and you won't go wrong.
  13. Yes. Any time you create or retrieve a page, whether it is a User type or any type of Page object, you should turn off output formatting before you save the data. For example: // new user, or any type of page object $u = new User(); $u->of(false); // turn off output formatting // assign data to fields $u->save(); // existing user, or any type of page ovbect. $u = $users->get("username"); // replace username with the name of a user $u->of(false); // turn off output formatting // assign data to fields $u->save(); ProcessWire will automatically turn output formatting on again after the save completes.
  14. Those ridiculous, downright stupid, pointless and idiotic EU Cookies taste like crap.
  15. I'm sure there is a ProcessWire way to do it, but I'm not skilled enough yet, so I settled for a document tree that looks like this: /home/policy/tos /home/policy/privacy /home/policy/aup ... which presents urls like, domain.com/policy/tos, etc. Those pages use the 'policy' template so that I can select or exclude them depending on which menu I'm rendering.