msummers Posted October 21, 2015 Share Posted October 21, 2015 I have inherited a ProcessWire site that was still in development when the webmaster was abducted by aliens. Forunately I have a zip file of the SQL dump and all of the files. I want to bring that dev site live (not public) so that I can complete development. Although I have not used ProcessWire in the past, I'm pretty good with Wordpress and after going through the PW documentation feel like I could pick the system up pretty fast. Here are my questions - I'd really appreciate any suggestions or help with them: I'm not sure what version of PW was running on the old server. How can I tell? I have not yet repointed the legacy domain name to the new nameservers so I am only able to access the new dev site by IP address - is this going to be a problem? What sequence of events should I follow to bring the old site up on the new server? For further context, I have created a database on the new server, changed the site/config.php file to reflect the new database properties and authentication, executed the SQL dump into the new database and copied the remaining files onto the new server. When I browse to the IP address, I just get a 404. Have I missed a configuration setting somewhere? Or is this related to the ip address for the new location? Thanks much in advance. I'd love to get the site functional on the new server if I can... Link to comment Share on other sites More sharing options...
kixe Posted October 22, 2015 Share Posted October 22, 2015 I recommend the following steps: make a new clean install of PW put your templates, assets, modules in the site folder download Ryans Module Database Backups here: http://modules.processwire.com/modules/process-database-backups/ go to Setup > Database Backups > Upload upload your sql If necessary reset admin password with the following code in your home template $users->get("admin")->setOutputFormatting(false)->set('pass', 'newpassword')->save(); look what happens. If needed switch on debug mode to clean-up your templates $config->debug = true; // in config.php Add your IP adress to HTTP hosts whitelist $config->httpHosts = array('xxx.xxx.xxx.xxx'); // in config.php 6 Link to comment Share on other sites More sharing options...
msummers Posted October 22, 2015 Author Share Posted October 22, 2015 Thank you so much for your helpful response. It has gotten me well down the road. I am still having issues, though: 1. I do not see the correct pages in the page list. For example, on the original dev site, there is "About Us" with 2 children (About and Team). On the new dev site, there are also 2 childen for About Us, but they are "Child Page example 1" and "Child Page example 2". 2. The pages that are there appear to have some of the correct layout elements (logo, background colors/images, etc.) but they do not have the sliders or the correct column layout. 3. I have a feeling that this is because I selected the default conmfiguration when I first installed ProcessWire. Could that be the problem? 4. Finally, how can I determine which version of PW is running on the original dev site? Thanks again for any suggestions! Link to comment Share on other sites More sharing options...
OrganizedFellow Posted October 22, 2015 Share Posted October 22, 2015 4. Finally, how can I determine which version of PW is running on the original dev site? Put this in one of your templates, <?php echo $config->version; ?> 3 Link to comment Share on other sites More sharing options...
msummers Posted October 22, 2015 Author Share Posted October 22, 2015 That's a good idea - unfortunately unless you can tell me how to edit those files from within the PW admin, I'm out of luck! I don't have file-level read/write permission to get at these legacy files otherwise (and not even sure I could do it then)! Is there a Readme file or something that could tell me? Link to comment Share on other sites More sharing options...
bernhard Posted October 22, 2015 Share Posted October 22, 2015 i think he wants to get the version of the old installation which is not running (only html + sql, right?)... you can find the old version number here /wire/core/ProcessWire.php: 32 class ProcessWire extends Wire { 33 34 const versionMajor = 2; 35 const versionMinor = 6; 36 const versionRevision = 1; 3. I have a feeling that this is because I selected the default conmfiguration when I first installed ProcessWire. Could that be the problem? was also my guess but i don't know to be honest. i would try it with blank-profile. good luck! edit: in admin you see the version on the bottom left corner 1 Link to comment Share on other sites More sharing options...
msummers Posted October 22, 2015 Author Share Posted October 22, 2015 The legacy version has had the Admin modified so that I don't see that information! But - the ProcessWire.php reveals that it's v2.3.0 - so, I wonder if any of my issues are caused by trying to use the 2.3.0 files (templates, modules, probably not assets) in my 2.6.1 installation? Link to comment Share on other sites More sharing options...
msummers Posted October 22, 2015 Author Share Posted October 22, 2015 Also, is there an easier way to change these profiles than the methods described in a 2014 thread I was just reading about doing this? https://processwire.com/talk/topic/8482-change-existing-installation-to-blank-profile/ Link to comment Share on other sites More sharing options...
OrganizedFellow Posted October 23, 2015 Share Posted October 23, 2015 @msummers How's the progress going? Link to comment Share on other sites More sharing options...
msummers Posted October 23, 2015 Author Share Posted October 23, 2015 I really don't know where to go from here. I think I'll try that migrator To get to the blank profile... Link to comment Share on other sites More sharing options...
OrganizedFellow Posted October 23, 2015 Share Posted October 23, 2015 I really don't know where to go from here. First: were you able to get a clean install running? Do that. Get your permissions set up http://processwire.com/docs/security/file-permissions/ Also there is a different setup if your Apache is version older than 2.4. It's commented in the $root/.htaccess file. Checkout lines 52-75. It explains there. I'm sure we can all help you get this up and running soon! hang in there 1 Link to comment Share on other sites More sharing options...
Peter Knight Posted October 23, 2015 Share Posted October 23, 2015 I have inherited a ProcessWire site that was still in development Cue lots of forums members checking their in-progress sites But seriously - Welcome to the forums and PW. Link to comment Share on other sites More sharing options...
Peter Knight Posted October 23, 2015 Share Posted October 23, 2015 That's a good idea - unfortunately unless you can tell me how to edit those files from within the PW admin, I'm out of luck! If it's template files you want to edit directly within the Admin, there is a Module available http://modules.processwire.com/modules/template-editor/ 1 Link to comment Share on other sites More sharing options...
msummers Posted October 23, 2015 Author Share Posted October 23, 2015 @Organized - Thanks for your optimism! I'm in fair shape. I was able to get a fresh install (2.6.1) running, copied the modules, assets and templates from the old site (2.3.0) into the new one. When I browse to the new site now, I see some things correct (background images, and colors), but I don't see others at all (sliders, correct pages in menu, regions of background images in body, content, etc.). I suspect that at least some of this is due to my selection of the default profile when I did the 2.6.1 setup. My next step will be to change that profile to the blank one (using that Migrator app - do you have a better suggestion?) to see if that helps. But I'm getting the feeling that I may have to copy fields and set up each template manually (and maybe modules too). Is that correct? The permission problem is on the legacy site, not the new one, and I'm not sure about Apache versions but I'm pretty sure . @Peter - Thanks for your welcome and suggestion. I will definitely bring in that template editor module! Link to comment Share on other sites More sharing options...
bernhard Posted October 23, 2015 Share Posted October 23, 2015 I would do a blank Installation of a pw 2.3 (you find the old versions on github) and change the site folder like explained above. A new installation is a matter of minutes. Trying to replace the profile is more pain I think. When you have your 2.3 site running I would install http://modules.processwire.com/modules/process-wire-upgrade/ (it says it is compatible with 2.3) and let it do the upgrade for you 2 Link to comment Share on other sites More sharing options...
msummers Posted October 23, 2015 Author Share Posted October 23, 2015 Has anyone used the Migrator module? Link to comment Share on other sites More sharing options...
msummers Posted October 23, 2015 Author Share Posted October 23, 2015 @Bernhard - didn't see your post before I made my last one. Your suggestion makes a good deal of sense. I'll try that... Link to comment Share on other sites More sharing options...
msummers Posted October 23, 2015 Author Share Posted October 23, 2015 @Bernhard - where on github do I find PW2.3? When I search I don't find it. Link to comment Share on other sites More sharing options...
kongondo Posted October 23, 2015 Share Posted October 23, 2015 @Bernhard - where on github do I find PW2.3? When I search I don't find it. https://github.com/ryancramerdesign/ProcessWire/releases 2 Link to comment Share on other sites More sharing options...
cstevensjr Posted October 23, 2015 Share Posted October 23, 2015 https://github.com/ryancramerdesign/ProcessWire/releases/tag/2.3.0 1 Link to comment Share on other sites More sharing options...
bernhard Posted October 23, 2015 Share Posted October 23, 2015 database backup/restore seems to be 2.5+ so it could get a little tricky to get the old data into the new installation. i would go with kixes solution but start over with a blank profile i'm still confused what was the problem with only using all the files + db dump... good luck and also welcome to the forum Link to comment Share on other sites More sharing options...
msummers Posted October 27, 2015 Author Share Posted October 27, 2015 Thanks, guys! I got it. We'll see where this gets me soon. 1 Link to comment Share on other sites More sharing options...
OrganizedFellow Posted October 27, 2015 Share Posted October 27, 2015 Thanks, guys! I got it. We'll see where this gets me soon. If you are able to, can you share and document here so that others with a similar problem? Link to comment Share on other sites More sharing options...
Craig Posted October 27, 2015 Share Posted October 27, 2015 I don't want to really confuse things here now, at this stage, but in this situation I would always recommend looking at everything you already have, and get that working first. Troubleshoot any and all problems that occur. Once that's stable and functioning, then go about upgrading and/or continuing development, saving progress or backing up as you go. That advice is not just relevant to ProcessWire, but whenever inheriting projects of any type. From experience, this minimises debugging and troubleshooting time, and the wondering if a particular problem was there previously, or if it's related to the new environment or upgrades. If any problems in upgrades or development do occur, you've only got one step (the last one you did!) to undo and get back to the last working state. I think using new versions and/or tools, in this situation and in this way, introduces several (unnecessary) points of failure which may not be immediately obvious and would only serve to throw spanners in the works 1 Link to comment Share on other sites More sharing options...
msummers Posted October 27, 2015 Author Share Posted October 27, 2015 @Craig - I think you are completely correct. My plan is to delete everything I have started, and install a 2.3.0 version (blank profile), then import the data, and ensure that everything is looking right before trying to move up to the latest version. Thanks for your nudge... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now