smart-syntax

Smart Syntax

Automatic google prettify syntax highlighting for jetpack markdown fenced code blocks

code blocks google prettify jetpack markdown markdown syntax highlighter

46.8 opportunity score Open evidence Open API Open on WordPress.org

10active installs

4.9Kdownloads

5.0rating

0unresolved threads

8complaints analyzed

3praise analyzed

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

27 / 37 rows with source links

73.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

10 rows with no attached evidence

0 rows have source counts but still need direct links.

Download Momentum

180 days

91recent 30 days 107previous 30 days -15.0%movement 578shown total

Related Opportunities

1 market

Needs sharper proof Syntax Highlighter: Content publishing operations content publishing operations · final 69.1 · proof not collected

Source Evidence

Open evidence explorer

complaint support · medium severity · relevance 0.81

use of undefined constant

use of undefined constant: users show bugs, compatibility, missing feature pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

use of undefined constant When I access the settings page, I get these errors: Notice: Use of undefined constant cdn_prettify – assumed ‘cdn_prettify’ in /wp-content/plugins/smart-syntax/includes/admin-menu.php on line 47 Notice: Use of undefined constant custom_skin – assumed ‘custom_skin’ in /wp-content/plugins/smart-syntax/includes/admin-menu.php on line

complaint support · medium severity · relevance 0.81

Version 1.0.1 does not work with 4.0.1?

Version 1.0.1 does not work with 4.0.1?: users show bugs, performance, setup pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

Version 1.0.1 does not work with 4.0.1?

complaint support · medium severity · relevance 0.75

function prettyPrint is not defined

function prettyPrint is not defined: users show bugs, compatibility pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

function prettyPrint is not defined Simple fix in smart-syntax/includes/functions.php line 46 <?php if (true === empty($smart_syntax['cdn_prettify'])) { ?> <script>prettyPrint()</script> <?php } ?> The error occurs when loading run_prettify.js from the google repository.

complaint support · medium severity · relevance 0.75

Homepage support

Homepage support: users show compatibility, support pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

Homepage support I didn’t work with my homepage (only on single post pages), so I removed the is_singular() check in functions.php and now it works!

complaint support · medium severity · relevance 0.75

Different class values for home page

Different class values for home page: users show bugs, support pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

Different class values for home page Hi, when I view my Home Page the <pre> tags are modified like this: <pre class="prettyprint lang-css"> or <pre class="prettyprint lang-csharp"> But when I select to view a single post the tags are slightly different: <pre style="" class="prettyprint lang-css prettyprinted"> or <pre style="" class="prettyprint lang-csharp

complaint support · medium severity · relevance 0.75

cannot access property of non object

cannot access property of non object: users show bugs, compatibility pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

cannot access property of non object I recently started receiving this error message at the top of my website: Cannot access property of non object in wp-content/plugins/smart-syntax/includes/functions.php at line 17 I modified the functions.php file like this to avoid getting the error: $content = ""; if(is_object($post) && is_object($comment) && property_e

complaint support · medium severity · relevance 0.69

Enable Smart Syntax with custom post types?

Enable Smart Syntax with custom post types?: users show compatibility pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

I like using it with Jetpack Markdown, but it’s not working in a custom post type within my theme.

complaint support · medium severity · relevance 0.69

typo in title string

typo in title string: users show missing feature pain that may indicate a product gap.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

typo in title string On the settings page, the title has a typo: Smart Synax Plugin Settings It should be: Smart Syntax Plugin Settings On the settings page, the title has a typo: Smart Synax Plugin Settings It should be: Smart Syntax Plugin Settings

praise review · medium severity · relevance 0.38

Does exactly what it says on the tin

Does exactly what it says on the tin: users praise value, which suggests what competitors already do well.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

Does exactly what it says on the tin Adds the required attribute values to the <pre> tag for google prettify to work – brilliant thanks.

praise review · medium severity · relevance 0.38

Perfect: users praise quality, which suggests what competitors already do well.

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

Investigate Pain card complete content publishing operations Evidence linked to opportunity

Perfect Till today, I didn’t activate JetPack Markdown as doesn’t use Google Prettyprint, but this plugin has now changed that!!

Competitor Context

1 shown

Code Manager praise owner · intel 64.6 · weakness 47.8

praise owner

11 collected complaint signal(s) support compatibility 2 source links Proof Blocked Evidence linked to opportunity

Buyer: site builders and agencies · Wedge: detect CSS Editor layout regressions, widget breakage, and client-visible update issues

source 1 source 2

Repeated Themes

0 shown

No repeated plugin-level themes have been generated yet.

Collected Signals

12 shown from 12 collected

complaint typo in title string support · 2017-06-28T01:23:41+00:00 · medium severity · code blocks

typo in title string: users show missing feature pain that may indicate a product gap.

Evidence: typo in title string On the settings page, the title has a typo: Smart Synax Plugin Settings It should be: Smart Syntax Plugin Settings On the settings page, the title has a typo: Smart Synax Plugin Settings It should be: Smart Syntax Plugin Settings

missing feature agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint use of undefined constant support · 2017-06-28T01:20:50+00:00 · medium severity · code blocks

use of undefined constant: users show bugs, compatibility, missing feature pain that may indicate a product gap.

Evidence: use of undefined constant When I access the settings page, I get these errors: Notice: Use of undefined constant cdn_prettify – assumed ‘cdn_prettify’ in /wp-content/plugins/smart-syntax/includes/admin-menu.php on line 47 Notice: Use of undefined constant custom_skin – assumed ‘custom_skin’ in /wp-content/plugins/smart-syntax/includes/admin-menu.php on line

bugs compatibility missing feature agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint cannot access property of non object support · 2017-06-28T01:09:05+00:00 · medium severity · code blocks

cannot access property of non object: users show bugs, compatibility pain that may indicate a product gap.

Evidence: cannot access property of non object I recently started receiving this error message at the top of my website: Cannot access property of non object in wp-content/plugins/smart-syntax/includes/functions.php at line 17 I modified the functions.php file like this to avoid getting the error: $content = ""; if(is_object($post) && is_object($comment) && property_e

bugs compatibility agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint Enable Smart Syntax with custom post types? support · 2017-04-07T17:12:39+00:00 · medium severity · code blocks

Enable Smart Syntax with custom post types?: users show compatibility pain that may indicate a product gap.

Evidence: I like using it with Jetpack Markdown, but it’s not working in a custom post type within my theme.

compatibility agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

praise max-height: 250px; is not necessary. (5 stars) review · 2015-12-24T07:09:59+00:00 · medium severity · code blocks

max-height: 250px; is not necessary.: praise conversation with limited structured signal.

Evidence: max-height: 250px; is not necessary. I want max-height: 250px; css removed. I want max-height: 250px; css removed. It makes your post is not very long! If you want unset max-height, you just add custom CSS! It makes your post is not very long! If you want unset max-height, you just add custom CSS!

agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint Homepage support support · 2015-03-29T11:33:30+00:00 · medium severity · code blocks

Homepage support: users show compatibility, support pain that may indicate a product gap.

Evidence: Homepage support I didn’t work with my homepage (only on single post pages), so I removed the is_singular() check in functions.php and now it works!

compatibility support reliable agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

praise Perfect (5 stars) review · 2015-03-29T11:29:26+00:00 · medium severity · code blocks

Perfect: users praise quality, which suggests what competitors already do well.

Evidence: Perfect Till today, I didn’t activate JetPack Markdown as doesn’t use Google Prettyprint, but this plugin has now changed that!!

quality agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint function prettyPrint is not defined support · 2015-02-19T05:29:33+00:00 · medium severity · code blocks

function prettyPrint is not defined: users show bugs, compatibility pain that may indicate a product gap.

Evidence: function prettyPrint is not defined Simple fix in smart-syntax/includes/functions.php line 46 <?php if (true === empty($smart_syntax['cdn_prettify'])) { ?> <script>prettyPrint()</script> <?php } ?> The error occurs when loading run_prettify.js from the google repository.

bugs compatibility easy agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

neutral It Didn't Work For ME support · 2015-01-07T19:57:46+00:00 · medium severity · code blocks

It Didn't Work For ME: neutral conversation with limited structured signal.

Evidence: It Didn't Work For ME I put the following code into a post and it came out not as code but as interpreted HTML <?prettify?> <pre class="prettyprint"> <h1>fred</h1> </pre> What else do I have to do to me it work? https://wordpress.org/plugins/smart-syntax/ I put the following code into a post and it came out not as code but as interpreted HTML <?prettify?> <p

agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint Version 1.0.1 does not work with 4.0.1? support · 2014-11-28T23:47:19+00:00 · medium severity · code blocks

Version 1.0.1 does not work with 4.0.1?: users show bugs, performance, setup pain that may indicate a product gap.

Evidence: Version 1.0.1 does not work with 4.0.1?

bugs performance setup form agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

complaint Different class values for home page support · 2014-08-01T16:03:59+00:00 · medium severity · code blocks

Different class values for home page: users show bugs, support pain that may indicate a product gap.

Evidence: Different class values for home page Hi, when I view my Home Page the <pre> tags are modified like this: <pre class="prettyprint lang-css"> or <pre class="prettyprint lang-csharp"> But when I select to view a single post the tags are slightly different: <pre style="" class="prettyprint lang-css prettyprinted"> or <pre style="" class="prettyprint lang-csharp

bugs support value agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin

praise Does exactly what it says on the tin (5 stars) review · 2014-08-01T15:18:21+00:00 · medium severity · code blocks

Does exactly what it says on the tin: users praise value, which suggests what competitors already do well.

Evidence: Does exactly what it says on the tin Adds the required attribute values to the <pre> tag for google prettify to work – brilliant thanks.

value agency visual QA and update safety Investigate Pain card complete Evidence linked to opportunity

Buyer: publishers, content teams, and agencies · Wedge: check syntax highlighter publishing, media, metadata, and editorial handoffs before content goes live

source plugin