Arkisto, elokuu 2018

Undefined property: stdClass::$post_type when adding a Link

12. elokuuta 2018 klo 18.18
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: WordPress

The plugin refers to $post->post_type before testing it exists, which triggers an error for WP’s built-in (though hidden-by-default since forever) ”link” post type. The error appears quite harmless, as it doesn’t seem to interfere with the link editor’s functionality in any way.

Setup

  • Simple Tags version 2.4.7
  • WP version 4.9.8
  • PHP version 5.6.33

Steps to reproduce

  1. Set WP_DEBUG on (define as true)
  2. Enable WordPress’ link manager (add_filter( 'pre_option_link_manager_enabled', '__return_true' );),
  3. Go to Links > Add New

What happens

Simple Tags’ Settings box in the sidebar shows the following notices:

Notice: Undefined property: stdClass::$post_type in [path to wp]/wp-content/plugins/simple-tags/inc/class.admin.post.php on line 46
Notice: Undefined property: stdClass::$post_type in [path to wp]/wp-content/plugins/simple-tags/inc/class.admin.post.php on line 54

Vastaa viestiin sen kontekstissa (Github)

Kemintien alikulussa liukasta raparällikköä

8. elokuuta 2018 klo 15.44
Sijainti: Muut: Oulun Palautepalvelu
Avainsanat: liikenne, turvallisuus

Kemintien alikulussa on ilmeisesti sateiden jäljiltä liukasta raparällikköä, jonka väistäminen pimeässä tunnelissa jalankulkijana kasvattaa riskiä jäädä pyöräilijöiden alle.

Vastaa viestiin sen kontekstissa (Oulun Palautepalvelu)

This does not reproduce under Wayland

6. elokuuta 2018 klo 17.06
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Chrome, Firefox, Gnome, Nextcloud, Signal, Wayland, Xorg

Alright, from my brief testing it would seem this does not reproduce under Wayland.

My recipe above appears to be quite sensitive to details: I have a test user with a clean desktop (with little more customization apart from the extension), and there the recipe works just as written. On the other hand, with my main user account it doesn’t. To clarify: while the steps listed above fail to reproduce the issue with my main account, my main account does manifest the issue too; just not with those exact steps.

My main account starts up the Signal desktop client, Nextcloud client and some other stuff upon login, but so far I haven’t found which of those (if any) causes this difference.

I was, however, able to reproduce the ”see-through hole” effect under both accounts: instead of maximizing Gnome terminal (in step 3), I tile it to cover the left half of my screen, then start up Chrome/Firefox, tile itover the terminal window (i.e. to also cover the left half of the screen), before turning the display off and on again. Firefox then also manifests the hole, as does Gnome terminal when brought back to foreground from below. (Chrome does not manifest the hole, but then again Chrome has always appeared oblivious to the extension here.)

I should mention that I’m leaving the display off for about 4-5 seconds before turning it back on again. I’m not sure if that makes any difference, I’m just doing to to be sure that the ”I’m off” signal has time to propagate back to the system.

 

Vastaa viestiin sen kontekstissa (Github)

I’ve only used Xorg too, but I may be able to try reproducing it under Wayland over the weekend

2. elokuuta 2018 klo 13.20
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Gnome, Wayland, Xorg

I’ve only used Xorg too, but I may be able to try reproducing it under Wayland over the weekend.

Vastaa viestiin sen kontekstissa (Github)

Ja tietysti vasta sen jälkeen kun viimeinenkin kielinatseilutilaisuus oli vastaajalta mennyt.

1. elokuuta 2018 klo 21.00
Sijainti: Muut: reddit
Avainsanat: kieli

”Vastauksesi ovat tallennettu”, ja tietysti vasta sen jälkeen, kun viimeinenkin kielinatseilutilaisuus oli vastaajalta mennyt.

Vastaa viestiin sen kontekstissa (reddit)