Gahapati

@hannanhazari

How to Set Up WP Downgrade

Before you start, DO MAKE SURE you have a working backup of both your files and your database! — Just in case …

1. After you’ve installed and activated WP Downgrade, head over to Settings → WP Downgrade.
2. When you first open the WP Downgrade Settings page, the heading reads WP Downgrade: Inactive
3. Fill-in the field WordPress Target Version with the WP version you wish to update/downgrade to.

• Make sure the version number you enter actually exists(!) by opening the link to WP Releases in a new browser tab and checking the list of WP releases.
• Though technically in German, the page simply shows a list of all WP releases. For some reason unknown, there does not seem to exist an English equivalent to this page. (The heading “Aktuellste Ver?ffentlichung” is Most Current Release in English. “Zweig” is branch.)

• Click Save Changes.

• Relax. This 1st step simply saves WP Downgrade’s settings.

• Upon saving changes the heading now reads something like WP Downgrade: Active (WP 4.6.5 is set as target version)

• Now that WP Downgrade is Active, it makes WP behave as though the version number you entered in step 3 were the most current WP release.
• Consequently, as long as WP Downgrade is Active, you will no longer be offered any automatic updates other than the one you specified.

• Next, click on either the link or the button that takes you to the WordPress Updates page (which is the same as Dashboard → Updates), where you will now be offered to “update” (even though you may be doing a downgrade) to the version number you specified on the WP Downgrade settings page.

• Remember: There can be no guarantee that a downgrades will be successful (that’s why you did make a backup first), simply because this is something WP was not actually built to do. However, since the process involved is the same WP core process which is used for updates, chances are high that things will go smoothly.
• Judging from feedback in the reviews, no-one so far seems to have run into issues while downgrading.

• This reply was modified 7 years, 7 months ago by Gahapati. Reason: Minor Corrections

In subsequent versions of WP Downgrade the default language has since been changed to English.

FWIW, I have Broken Link Checker 1.11.2 running under PHP 7.0.16 and WP 4.4.8, and so far I haven’t seen any warnings related to it (I often debug plugins with debug mode on) or experienced any quirks.

Just wanted to update this by adding that this bug has no longer been showing since I updated WP to 4.4.x.

I’m at a loss for a description in abstract terms.

An example of how this may be applied can be found on the settings page in both the English and German versions. (The comparison of the two may provide additional clues.)

The description states:

You may also use some more sophisticated, conditional placeholders:

• *modification_times* and *conditional_no*.

With these two placeholders you should be able to formulate a single sentence to accommodate three conditions a post may have:
having had either zero, one, or more than one modification.

Setup Example: This document, published *publication_timestamp*, has *conditional_no* been modified *modification_times* since; last on *last_modified_timestamp*.

The above example should render as either:

• This document, published 10/01/2015, has not been modified again since; last on 10/01/2015.
• This document, published 10/01/2015, has only been modified once since; last on 09/31/2016.
• This document, published 10/01/2015, has as yet been modified 9 times since; last on 09/31/2016.

Die deutsche Beschreibung lautet:

Sie k?nnen auch ein Paar anspruchsvollerer, bedingter Platzhalter verwenden:

• *modification_times* und *conditional_no*.

Diese beiden Platzhalter erlauben es Ihnen, einen ?nderungshinweis zu formulieren, der sich drei verschiedenen m?glichen Zust?nden eines jeden Beitrags anzupassen vermag:
entweder nie, einmal oder mehrmals bearbeitet worden zu sein.

Beispiel-Formulierung: Dieses Dokument vom *publication_timestamp* wurde seitdem *conditional_no* *modification_times* bearbeitet; zuletzt am *last_modified_timestamp*.

Obiges Beispiel würde etwa ergeben:

• Dieses Dokument vom 01.10.2015 wurde seitdem nicht mehr bearbeitet; zuletzt am 01.10.2015.
• Dieses Dokument vom 01.10.2015 wurde seitdem genau einmal bearbeitet; zuletzt am 31.09.2016.
• Dieses Dokument vom 01.10.2015 wurde seitdem bisher 9-mal bearbeitet; zuletzt am 31.09.2016.

• This reply was modified 7 years, 11 months ago by Gahapati. Reason: Formatting
• This reply was modified 7 years, 11 months ago by Gahapati. Reason: Formatting
• This reply was modified 7 years, 11 months ago by Gahapati. Reason: Formatting
• This reply was modified 7 years, 11 months ago by Gahapati. Reason: Minor Addition

Thanks, Greg.

you should never have to include the pluggable file manually.

Yes, I thought as much.

Strangely this kind of error has never come up before.

So, I guess I’ll remove that include_once() again and see if I get any clues as to who the culprit may be.

Thank you for answering me, David!

It’s good to see you are still supporting this plugin.

Here we use latest version of wordpress and the plugin works just fine.

May I suggest to you that you push an updated readme.txt to the repository with the corrected version number?!
It is very helpful for users to be able to see up to which version developers think their plugins are compatible. It also shows us, whether a plugin is still “alive”.

Which is the main problem with the plugin in your set up?

1. Verify Subdomains does not seem to work at all.
   When I click on it, I’m being warned about an insecure connection (I’m running all domains on Let’s Encrypt SSL). When I click OK, the options page reloads, and that’s it. I checked the file domain.check.valid.txt, and it contains the single string “valid”.
2. Use protocol less urls does not seem to be having any effect. The page source stays unchanged, regardless of setting.
   This might, however, be due to the SSL plugin I’m using (Really Simple SSL), I’m not sure. I have, since my initial post, changed my sub-domain setup from wildcard to “true” sub-domains which each have their own DNS record and associated SSL cert.
3. Paths to images (are not) were not replaced, until I happened to read another support threat (Issues with php 7).
   After I removed the reference by changing function check_domain_sharding(&$buffer) to just function check_domain_sharding($buffer) — voila, images are being served from all five of my cdn-subdomains now.

This is the warning I got before I made the change (I’m also running on PHP 7.0.x, by the way):

PHP Warning: Parameter 1 to domain_sharding::check_domain_sharding() expected to be a reference, value given in /wp-includes/functions.php on line 3464

I think this shows there is still some room for improvement ??
I am glad, though, that Domain Sharding now at least does its main trick.
Still, it would be reassuring if you could fix the remaining issues.

Thanks for your time and effort!

Hi!

not sure what is different between then and now.

I’m not surprised, really, that you don’t know what you did that makes it work now.
I can certainly relate to that. In software development sometimes funny things happen. In my (since long by-gone) times as active developer (of some fringe PHP CMS) it sometimes happened that, when people requested features, it turned out they were already there, unbeknownst even to core devs. All it took was to point out the steps necessary to use those features.
— But I digress.

I was under the assumption that some site-admin …

There are none besides me. And, as I implied, it just wouldn’t install correctly, and even after I set up tables manually, the UI was completely dysfunctional for no apparent reason.

But in the end what counts is that it does work now. Just please do not make it not work again! ??

About translations: Well, I’d say: go for it! (Lest I change my mind.) ??

I should just add this teeny “word of warning”:
The language style I’m aiming at is none-too-modern. I’m out of school, hold no office and therefore need not abide by the New German Orthography (which, in any case, is neither new, German, nor orthographic). I’m trying to avoid anglicisms as much as possible. This includes WordPress’ish expressions like dashboard, widget, and theme, which I do not leave untranslated, but substitute by the German equivalents of control-panel, component, and motif.

That said, I’d be glad to help.

Hi, Marcel!

Thank you for looking into this at the time. I did try a lot of things then myself, including manually creating the missing SQL-tables. (And, No, there was no permissions problem. My hosting provider is quite liberal in this regard.) I gave up for the time being, when all I did was to no avail.

It seems, though, you have been quite busy coding meanwhile.

I just now happened to give your plugin another try, and I’m glad to be able to report that, voila, all of a sudden, without me having done anything additionally in the meantime that could have affected this, Gwolle Guestbook actually works!

So, thank you very much for whatever it may be that you did, but you did it!

Now, if this translate.www.remarpro.com Glot-thing wasn’t such a pain, I’d be glad to contribute to the missing portions of the German (Formal) translation, which I’m just now about to finish. But I’m afraid I can’t bring myself to type in manually 497 lines of text, when uploading a pair of .po/.mo-files from Poedit Pro would take just a few seconds. (I don’t know how come these last ten years or so modern must always mean less usable…) Do you know of any way to get text into translate.www.remarpro.com without so much trouble?

I had to create an empty menu on the child site and assign it to the appropriate location, and then it worked.

Thank you for pointing this out. I was about to throw this one out. Should have been in the plugin’s description, really.

What’s unfortunate, though, is that it only really copies menu locations not menus as such. I was hoping to pull in a menu that’s being displayed not in one of the menu locations but within a widget…

I packaged the corrections/additions as roasted-url-shortener 1.0.1, which you can download from Dropbox here.

There’s a typo in urlshortener.php line 11, which incorrectly reads

require_once("urlshortnerdb.php");

when it should in fact read

require_once("urlshortenerdb.php");

(Note the missing letter ‘e’.)

Also, Roasted Url Shortener‘s minimum requirement is WP 4.4, not 3.0 as claimed.

Fortunately, though, all that is “wrong” is a missing function, which got introduced in WP 4.4, and which can easily be added to urlshortener.php, if your’re not running WP 4.4 yet.

Before (or after) the first line of code, which correctly reads

require_once(“urlshortenerdb.php”);

put the following (taken from here):

if (!function_exists('wp_parse_url')) {
	function wp_parse_url( $url ) {
    $parts = @parse_url( $url );
    if ( ! $parts ) {
        if ( '/' == $url[0] && false !== strpos( $url, '://' ) ) {
            if ( ! $parts = @parse_url( 'placeholder://placeholder' . $url ) ) {
                return $parts;
            }
            unset( $parts['scheme'], $parts['host'] );
        } else {
            return $parts;
        }
    }

    if ( '//' == substr( $url, 0, 2 ) && ! isset( $parts['host'] ) ) {
        $path_parts = explode( '/', substr( $parts['path'], 2 ), 2 );
        $parts['host'] = $path_parts[0];
        if ( isset( $path_parts[1] ) ) {
            $parts['path'] = '/' . $path_parts[1];
        } else {
            unset( $parts['path'] );
        }
    }
    return $parts;
	}
}

Other than that – I think Roasted Url Shortener really is a great plugin!!

I just updated again from 2.2.8 to 3.0.2.

As far as I can tell, all seems well, now.

Thank you! And thanks for the quick response, too!

Das ist ja richtig gro?artig!

Die Sprachattributsvarianten-Fehlerbehebung (Language Attribute Variant Fix) ist bei mir ab sofort als MU-Plugin im Dauereinsatz.

Vielen herzlichen Dank!

Unfortunately, that is my experience, too.

It actually used to work just fine – back in the olden days of WP 3.3.

Ever since I updated to WP 4.x Allow Multiple Accounts broke on my WP Multisite.

It would be great to have this back!