chris howard

Thanks, Riddhi

I setup a staging site to test that.

And yes, it breaks TwentyTwenty theme too.

In fact, it breaks the WP block editor when I enter the shortcode.

I tried creating a new one and it still breaks.

Tracked down the error logs. Here’s what it shows

Stack trace:
#0 /www/wp-content/plugins/countdown-timer-ultimate/includes/shortcode/wpcdt-shortcode.php(34): DateTimeZone->__construct(”)
#1 /www/wp-includes/shortcodes.php(343): wpcdt_countdown_timer(Array, ”, ‘wpcdt-countdown’)
#2 [internal function]: do_shortcode_tag(Array)
#3 /www/wp-includes/shortcodes.php(218): preg_replace_callback(‘/\\[(\\[?)(wpcdt\\…’, ‘do_shortcode_ta…’, ‘\r\n<p>It has bee…’)
#4 /www/wp-includes/class-wp-hook.php(287): do_shortcode(‘\r\n<p>It has bee…’)
#5 /www/wp-includes/plugin.php(206): WP_Hook->apply_filters(‘\r\n<p>It has bee…’, Array)
#6 /www/wp-includes/post-template.php(253): apply_filters(‘the_content’, ‘<!– wp:paragra…’)
#7 /www/wp-content/themes/twentytwenty/template-parts/content.php(36): the_content(‘Continue readin…’)
#8 /www/wp-includes/template.php(732): require(‘/www/wp-content…’) in /www/wp-content/plugins/countdown-timer-ultimate/includes/shortcode/wpcdt-shortcode.php on line 34

Ah! Ignore that! I see why. You only do it for double spaced. Tho I can’t say it was working for them consistently either.

I want a version for converting single spaces to double – which I now have with my hacked version! Thanks.

Thanks. I guess that’s going to be a problem with plugins… they might work with 5.x but doesn’t mean they work with GB.

Thanks, Tammie

I have already installed and activated Classic Editor on all our sites in preparation for 5.0.

I do think there would be value in including a block that allows multiple paragraphs.

And of course, making GB opt-in.

BTW Where has the author field gone in GB editor?

Oh! Discovered that even after deactivating and deleting Health Check through the plugins screen, my site still goes 500 when I reactivate the child theme. So, HC still has its claws in my site even after it’s gone.

Hi Marius

The site could actually be considered destroyed – as other commenters her have also encountered – in terms of requiring some unknown and difficult database hack to recover it. Like others, I tried removing the Health Check plugin.

Without knowing the hack, the recovery process would be to wipe WordPress entirely (since it’s corrupted) including all files and the database, and then reinstall as per the backup used.

I didn’t bother with a backup since the site was just a staging site, so I can just wipe it and restage it.

But Health Check is intended to run on live sites. And yet you need to test it before installing it… To do that you need to stage your site. If I’m going to have to stage my site anyway, I can then troubleshoot the site the usual way. So, why do I need Health Check?

For it to be useful it needs failsafe switch to quickly turn it off if it breaks a site.

For your info, I just renamed my child theme folder (so WP wouldn’t then find it) and the site is now un-nuked. So, can confirm my site’s issue was child theme related. (Tho, I though HC automatically switched to Twenty Seventeen?)

I will give HC another look but will still be very wary

Thanks, Bill. Might be a plugin conflict then. Will test that first and log a ticket either way.

“after we activate absolutely nothing changes”

No, there’s a page for Redux in your Tools menu now.

Redux is for developers, not users. 99% of people using it know that. Hence, there won’t be any concerning increase in 1 votes.

From time to time, there will be some people like yourself who misunderstand that and inadvertently install. I dont’ work for Redux, but on behalf of them, sorry for any confusion.

If you’re not a developer building themes or plugins, you have no need at all for Redux.

However, as Redux is essentially an add-on library of functions, a theme or plugin can *require* Redux is installed for that theme or plugin to work.

Does that help?

+1 Global CSS styling is affecting WordPress and other plugins.

Please isolate your styling to only your plugin’s elements.

Ta

Mike

I hit this problem when I updated to WC 2.3.x today with my own plugin.

It is being triggered in a loop of mine that is using a custom query.

Here’s the last few lines of xdebug:

13	0.5724	32565112	get_the_title( )	../arc-functions.php:763
14	0.5726	32565600	apply_filters( )	../post-template.php:158
15	0.5730	32567496	call_user_func_array:{/Users/xxxxxxxxxxxxx/architect-development/wp-includes/plugin.php:213} ( )	../plugin.php:213
16	0.5730	32567664	wc_page_endpoint_title( )	../plugin.php:213
17	0.5730	32567736	is_main_query( )	../wc-page-functions.php:19

Here’s the code whole loop:

$query_options    = array(
        'post_type'      => 'arc-blueprints',
        'meta_key'       => '_blueprints_short-name',
        'posts_per_page' => '-1'
    );
    $blueprints_query = new WP_Query($query_options);
    $pzarc_return     = array();
    while ($blueprints_query->have_posts()) {
      $blueprints_query->next_post();
      $the_panel_meta        = get_post_meta($blueprints_query->post->ID);
      $bpid                  = $the_panel_meta[ '_blueprints_short-name' ][ 0 ] . ($inc_post_id ? '##' . $blueprints_query->post->ID : '');
      $pzarc_return[ $bpid ] = get_the_title($blueprints_query->post->ID);
    };

and here’s a dump of the object:

object(WP_Post)[1695]
  public 'ID' => int 3561
  public 'post_author' => string '1' (length=1)
  public 'post_date' => string '2015-02-18 01:28:13' (length=19)
  public 'post_date_gmt' => string '2015-02-18 01:28:13' (length=19)
  public 'post_content' => string '' (length=0)
  public 'post_title' => string 'test' (length=4)
  public 'post_excerpt' => string '' (length=0)
  public 'post_status' => string 'publish' (length=7)
  public 'comment_status' => string 'closed' (length=6)
  public 'ping_status' => string 'closed' (length=6)
  public 'post_password' => string '' (length=0)
  public 'post_name' => string 'test' (length=4)
  public 'to_ping' => string '' (length=0)
  public 'pinged' => string '' (length=0)
  public 'post_modified' => string '2015-02-18 05:54:00' (length=19)
  public 'post_modified_gmt' => string '2015-02-18 05:54:00' (length=19)
  public 'post_content_filtered' => string '' (length=0)
  public 'post_parent' => int 0
  public 'guid' => string 'https://localhost/architect-development/?post_type=arc-blueprints&p=3561' (length=76)
  public 'menu_order' => int 0
  public 'post_type' => string 'arc-blueprints' (length=14)
  public 'post_mime_type' => string '' (length=0)
  public 'comment_count' => string '0' (length=1)
  public 'filter' => string 'raw' (length=3)

The error is triggered on the get_the_title() code.

I’ve replaced it with

$pzarc_return[ $bpid ] = $blueprints_query->post->post_title;

and the error has gone away, but then of course, I aren’t getting to pass the title thru the title filter. If I do so myself in code, it brings back the error.

I also tried get_the_content, and get_the_excerpt which as expected returned empty strings; however, get_the_id and get_the_date returned false.

I hope there’s some clues there.

On “static front page.

All pages are static “page 1 of 1 pages” but pagination works on them. It’s only the “static front page” where you need special code to make pagination work.

Sometimes, some people do want a front page that is a blend of static content and paged posts.

To that end, that instruction page on Pagination tells you how it *should* work. To quote the whole section:

static front page

If the pagination is broken on a static front page you have to add the “paged” parameter this way:

<?php
if ( get_query_var('paged') ) { $paged = get_query_var('paged'); }
elseif ( get_query_var('page') ) { $paged = get_query_var('page'); }
else { $paged = 1; }

query_posts('posts_per_page=3&paged=' . $paged);
?>

But without the global $paged; it doesn’t work for me.

Checked and this has been fixed for the next release which will hopefully be soon!

you can’t please everyone

That is a key point and one that WP – and any developer – needs to respect for their own sake, to keep them aligned with their mission.

I think T13 and T14 were trying to please specific groups of users. It wouldn’t surprise if those two had a much less usage rate than T11. T13 and T14 were more challenging to build upon, because they were already taken a long way in a specific direction.

There are so many great stylized themes for WP, it doesn’t need to, nor should, compete.

WP is a platform to build upon, I think its built-in theme should be too.

That said, I would like it to have much more customization options so newbies can DIY without having to write a child theme. T14, for example, would have benefitted greatly from multiple colour schemes, instead of just green and black. Or where it provided the option to change colours – have a lot more than just site title and body background.

TwentyEleven was the best theme WP has done. It had a great balance between usability, genericness, minimalism, and being ready to go. And it looked good. It was well equally usable by both newbies and developers.

Although, as a developer, TwentyTwelve was best for me because it had no clutter or wild formatting, but it was awful for newbies who just wanted to get their website up and running and looking pretty. I still use it in development.

And then came the antithesis in TwentyThirteen. TwentyThirteen andTwentyFourteen weren’t generic enough. (They had some whacky layout methods and formatting too that were a pain to work with).

TwentyThirteen was WP’s experimental uni-student phase; TwentyFourteen was its “first job, trying to impress the boss” phase.

So, hopefully TwentyFifteen will be like TwentyEleven but styled for 2015. Clean, elegant, usable, flexible and generic.

As I said, Photoshop defaults to the hue in the primary slider

https://www.screencast.com/t/7U7GDDFlT

So does Sketch

https://www.screencast.com/t/8DG1qXHuee