Jump to content
psy

JSON+LD Schema module

Recommended Posts

This module helps you dynamically create schemas for improved SEO & SERP listings from within your templates. Each schema can be configured to meet your requirements. You can even add your own ProcessWire schema classes to the module.

Read about the module on  github: https://github.com/clipmagic/MarkupJsonLDSchema

Download from github: https://github.com/clipmagic/MarkupJsonLDSchema/zipball/master

Download from ProcessWire modules: http://modules.processwire.com/modules/markup-json-ldschema/

  • Like 14

Share this post


Link to post
Share on other sites

Am I missing something? Where is that module? Do you have a link? Maybe I'm confused by the new forum changes, but I don't see an attachment either...

Share this post


Link to post
Share on other sites

Most of the time people do not only submit the module to the modules directory, but also link to either the module's page in the directory or the github repo (sometimes both) from their forum posts as well. Especially as it seems like your module is by not not approved in the module's directory nobody but you can see it there.

Share this post


Link to post
Share on other sites

OK. Still learning. Thanks.

Submitted module via github and had to open a forum topic as part of that process. Hopefully sorted now.

Let me know if I need to do more to make the module available.

 

Share this post


Link to post
Share on other sites

Hi @psy- thanks for creating your module. Could you also please edit the Github link to go to: https://github.com/clipmagic/MarkupJsonLDSchema/ instead of linking directly to the zip. That way we can read more about and can more easily choose how we might want to get/install it.

Thanks!

Share this post


Link to post
Share on other sites

Links added and closing tags removed.

I updated the version # to 0.0.3 but it is still showing 0.0.2 in the modules directory?

Thank you all for your help. Much appreciated. :)

Share this post


Link to post
Share on other sites

The modules directory visits github once a day. To force it to refresh, just edit the module in the directory, but don't do anything and just save. That forces the crawler to go back to github and voila, you got it updated :)

 

Congrats on your new module btw ^-^

  • Like 2

Share this post


Link to post
Share on other sites

Have not checked out the module yet, but seems like a very nice addition. The JSON+LD Schema is really something Google will be using a lot in the future. Mark my words!

  • Like 1

Share this post


Link to post
Share on other sites

This is a very nice module,  but when I try to validate a LocalBusiness schema using Google Search structured data tester, it don't validate. I got some error message like: Google doesn't recognise property streetAddress for an object of the type LocalBusiness. Same for addressLocality , addressRegion, .... Got the same problem when I try to valicate an article. Thank's for your help!

Share this post


Link to post
Share on other sites
11 hours ago, Pino said:

This is a very nice module,  but when I try to validate a LocalBusiness schema using Google Search structured data tester, it don't validate. I got some error message like: Google doesn't recognise property streetAddress for an object of the type LocalBusiness. Same for addressLocality , addressRegion, .... Got the same problem when I try to valicate an article. Thank's for your help!

Oh, yes you're correct. According to the reference, addresses are associated with Organization, not localBusiness. I will fix and update the module.

https://developers.google.com/schemas/reference/types/Place

https://developers.google.com/schemas/reference/types/LocalBusiness

Thanks for bringing this to my attention.

 

  • Like 1

Share this post


Link to post
Share on other sites

@OllieMackJames

Glad you like it :)

There are way too many schemas for me to include in the basic module. I chose what I thought would be the most useful. However you have a couple of options:

1. Use the custom schema option, eg:

$jsonld = $modules->get("MarkupJsonLDSchema");
$options = array();
$options["@type"] = "VideoObject";
$options["custom"] = array (
  "actor" => "Barney Rubble",
  "caption" => "What an actor!",
  ...
);
?>
<script type="application/ld+json">
  <?php $jsonld->render('Custom',$options); ?>
</script>

OR

2. Write your own schema and add it to the site/modules/MarkupJsonLDSchema/schemas/ directory. See the other schemas in there and their naming conventions as examples, and feel free to include your video schema code in this topic to share with others.


BTW, the link http://jsonld.com/video/ leads to a 404 Error. A much better resource is http://schema.org/VideoObject.

Hope this helps
psy
  
 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @psy,

Thanks for sharing your module!  I've been trying out your module and I'm aware that I don't have to use the default schemas and can use overrides, but I have a few questions:

Share this post


Link to post
Share on other sites

@gmclelland Thanks for the feedback . This was my first module, dipping my toe in so to speak. I found the whole schema thing confusing and the module could definitely do with an update. Have taken your suggestions on board - plus a few other things I've learnt about json-ld schemas in the interim - and hope to release an update in the new year

Share this post


Link to post
Share on other sites

Good to hear psy!  Looking forward to trying it.  I just started learning about JSON-LD, and your module and readme.txt with the links helped point me in the right direction.

19 hours ago, psy said:

I found the whole schema thing confusing

I've found it very confusing as well.  The JSON-LD and Google documentation doesn't exactly say when or what pages you should use Website schema vs Webpage.  Does the Organization markup go on every page, or just the homepage of the website? etc..etc...

  • Like 1

Share this post


Link to post
Share on other sites

I keep getting undefined index 'image'

Tried several ways to get rid of this error.

What is recommended/correct way to add the code for the images in the template?

Share this post


Link to post
Share on other sites

Hello Psy,

I currently have this and it looks like images are outputted

I must have made a stupid mistake somewhere. On another site I got it working in one time.

 

    $jsonld = $modules->get('MarkupJsonLDSchema'); ?>
    <script type="application/ld+json">
<?php
        switch ($page->template) {

            case 'product':

                $options = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'image' => $page->images->first()->size(200, 200)
                );
                echo $jsonld->render('Product', $options);
                //  echo $jsonld->render('BreadcrumbList');
                break;
            case 'categorieen':
                $options_c = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'description' => $page->summary,
                    'image' => $pages->get(1092)->images->first()->size(200, 200)
                );
                echo $jsonld->render('Product', $options_c);
                echo $jsonld->render('BreadcrumbList');
                break;
            default:
                $options = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'image' => $page->images->first()->size(200, 200)
                );
                echo $jsonld->render('WebPage', $options);
                echo $jsonld->render('LocalBusiness');
                echo $jsonld->render('BreadcrumbList');
                break;
        }
        ?>
    
    </script>

Share this post


Link to post
Share on other sites

Thanks for sharing @webhoes

Glad it's working for you.

Schema's are confusing and you can always write your own and add them to the schema dir of the module (and share here of course!)

One thing you may want to check... you're outputting several schemas within one <script> tag... maybe you need to enclose them in brackets, eg:

<script>[
    .... your output schemas ....
]<script>

to show multiple json arrays within one script tag. No expert here and would appreciate comments/recommendations from others.

Cheers

psy

 

 

Share this post


Link to post
Share on other sites

I don't understand them either. Was just working based of the sample's. I googled and it does not seem to matter if you use one block or more. I did quick and dirty fix... looking like this. Note I always have atleast 2 schemes and therefor kinda hardcoded the brackets. There is also a ',' between 2 schemes.

  <?php
    $jsonld = $modules->get('MarkupJsonLDSchema'); ?>
    <script type="application/ld+json">[
<?php
        switch ($page->template) {

            case 'product':

                $options = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'image' => $page->images->first()->size(200, 200)
                );
                echo $jsonld->render('Product', $options) . ",";
                echo $jsonld->render('BreadcrumbList');
                break;
            case 'categorieen':
                $options_c = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'description' => $page->summary,
                    'image' => $pages->get(1092)->images->first()->size(200, 200)
                );
                echo $jsonld->render('Product', $options_c) . ",";
                echo $jsonld->render('BreadcrumbList');
                break;
            default:
                $options = array(
                    'logo' => $pages->get(1)->logo->size(200, 200),
                    'image' => $page->images->first()->size(200, 200)
                );
                echo $jsonld->render('WebPage', $options) . ",";
                echo $jsonld->render('LocalBusiness') . ",";
                echo $jsonld->render('BreadcrumbList');
                break;
        }
        ?>

    ]</script>
  • Like 3

Share this post


Link to post
Share on other sites

BTW, if you use width() you get a cached image with name-200-0.jp. That means it has no height and therefor is not really an image. Using size() gets a correct image.

 

 

  • Like 2

Share this post


Link to post
Share on other sites

I was reading a thread about Structured Data, is it possible to use this module to generate the AggregateRating? 

See MarcoPLY example. Thank you.

 

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...