Pixeldust Drupal Support Service

How to utilise isDefaultRevision() for forward revisioning?

Since “Support revisions in different states” went into the core it is now theoretically possible to have forward revisions of nodes. For example publish revision 1 then create revision 2 but keep it unpublished. This is very useful when someone needs to create new version of a node that needs to be approved before publishing.

Sounds great so here’s what I did:

  1. I’ve created a node with title “Published revision”. The node ID is 1 and it’s revision is 1.
  2. I’ve created a new revision of node 1 and changed it’s title to “Unpublished revision”. This node has revision 2 and it has immediately been set as default revision.
  3. At this moment /node/1 shows the node with title “Unpublished revision”.
  4. I’ve used PHP to load node 1 with revision 1 and I’ve set it to default revision ($node->isDefaultRevision(true)).
  5. At this moment /node/1 shows the node with title “Published revision”.

So far so good. However the problem is that I’d like to edit revision 2 but I can’t:

  1. /node/1/edit shows edit form of revision 1.
  2. /node/1/revisions/2/edit is of course 404.
  3. And on top of that when I go to /node/1/revisions the revision 2 is listed as “Current” which of course is not true because default revision is 1. (Let’s say I can live with that for now)

Questions:

  1. How to edit arbitrary node revision?
  2. How to control which node revision is saved as default revision?
Sponsored by SupremePR
This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

Let's Talk About a Project

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

How to utilise isDefaultRevision() for forward revisioning?

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.
MASTER YOUR DRUPAL SEO
Pixeldust and Pantheon Drupal Development
256