In terms of this week’s readings, I’ll echo Allie’s thoughts in that I understand the general purpose of APIs, but, like she pointed out in her post, I’m not quite sure how they apply to our final projects and am a little confused on the more minute details, like resting APIs and JSON.
I have to say I’m feeling a little discouraged about our final project. I had issues over the weekend with my MAMP not starting the servers when I prompted it to and couldn’t access my local site. I was able to figure out how to get the app to work with a few hours of Googling and was feeling pretty good (and like a real web developer – yay!) but quickly realized that I’ve now stumbled on a new issue that’s still preventing me from accessing my local site.
My new problem is that when I run my local server and type in the address for my project (http://localhost:8888/finalproject/), I’m taken to the wp-admin page below:
I’m a little confused about why I’m seeing this page because it was my understanding that we had already installed WordPress in class together a few weeks ago? When I go through the final steps of installing WordPress here, I get a page showing me a bunch of database errors telling me certain files don’t exist:
And finally, when I click “login” at the bottom of the errors page, I get the following error message on a new page:
So far, Google has been unsuccessful in helping me figure out what’s wrong.
I didn’t want to lose time so I’ve continued to make changes to the code in my htdocs, even though I can’t preview it to see if the changes are correct. I created a child theme last week and have been working on creating a custom post type, which is probably my most complex customization. As suggested, I’m modifying this book list plugin.
I will keep Googling to see if I can find a solution, and, hopefully, I can get the local site issue resolved before Wednesday or can get help fixing it during class. In the meantime, I have a few other questions:
- We talked about how some of the more superficial changes should be made on our live site, rather than our local site because the changes won’t necessarily transfer over, and I want to know when we can do that? Should we wait until we make all of our more back-end changes or can we go ahead and make these smaller changes to our other site now?
- I think we may have covered this in class as well, but how often should we be saving the changes we are making to our GitHub repository? Is it enough to save it after we’ve completed a customization or should it be more frequent?
We’ll chat more about APIs in class, for sure!
If you’re not able to access wp-admin on localhost, then you’re not able to make any of those changes anyway 🙁 Everything that’s code-related, should be done first. After the code updates are done, then I’d recommend doing admin-based updates.
The exception there, of course, is adding some sample content to make sure everything looks as expected. With content, you can export that from localhost and import it to the live site. Unfortunately, most general settings in the admin will have to be re-done by hand if done locally.
Each GitHub commit should related to a specific thing being done (add X feature, update Y styles, fix Z error) as it’s complete, so no hard frequency there. How often you publish those commits to GitHub.com isn’t important unless you’re looking for feedback, as long as it’s all there by the deadline.