Jetpack Tiled Gallery Example
The Concept FeedWordPress is the plugin that allows us to create our “mother blogs.” Consider it an example of the “you are what you eat” concept. The “mother blog” is composed of the consumed feeds. FeedWordPress is our spoon. The mother takes all the student posts from their personal sites and unites them in one place. It helps answer questions like – How can students work in their own sites and use them for multiple courses but still provide the class/cohort advantages of a central/standardized community hub? How can I allow personalization but not go crazy going to 50 different student sites with different layouts? Are there interesting ways I might reconsider the work students do if I can aggregate that work, can provide different lenses of focus, can keep it beyond the narrow confines of a course, and have other students use it in interesting ways? A Brief Overview of the Mechanics Some Tips The child (source) blog needs to be public for this to work. If a child blog is set to Visible only to registered users of this network, Visible only to registered users of this site, or Visible only to administrators of this site then the feed won’t work. Here is how you change that. Add /feed/ to the URLs you’re adding as children in the […]
This happened with one of our individual installs and it’s happened before (but I forgot the solution) so I’m writing it down. After the upgrade to 4.7.1, the front of the sight still worked but attempts to get to wp-admin failed with a 500 error and the URL was redirecting to something with upgrade.php? in the URL. Solution Change the name of the plugin folder (I just prepend an underscore). Revisit your login URL. Run the database upgrade as prompted. You should now be in the admin zone. Fix your plugin folder name. Easy but also easy to forget.
I’ve been having quite a few conversations around student portfolios eportfolios online representations of their learning over time. These conversations have mostly centered on using WordPress and, almost inevitably, the first instinct is to create a series of pages that are aligned to either courses or assignments. Those pages usually contain a number of different pieces of content. That structure makes the most sense to people who are used to building websites in the Dreamweaver/static paradigm. I don’t think this is the right path in most cases. It’s easy in the short term but starts to limit you (absent lots of work) in the long run. Strange that I don't really know what a web page is anymore. Individual tweet? Blog post? Flickr image? #vcuols — Tom Woodward (@twoodwar) May 14, 2014 At the heart of this is the issue that “page” is hard to define. In the broadest sense anything I can address with a URL is a webpage. That’s a big bucket. WordPress makes things more complex by including a way to create pieces of content called “pages.” Pages are usually contrasted to posts. I usually describedPast tense the page/post difference was that posts were pieces of content that flowed with the timeline (more ephemeral but archived) and pages were pieces of content you wanted to be more […]