Jump to content
Nico Knoll

MarkupSEO - The all-in-one SEO solution for ProcessWire.

Recommended Posts

It seems that opengraph tags require "property" instead of "name" in tags:

http://ogp.me/

Here is a quick fix (around line 330, added dynamic $attributeName):

// add "render"
$rendered = '';
foreach($pageData as $name => $content) {

	// set "property" as meta attribute name instead of "name" if it's an opengraph tag
	$attributeName = strpos($name, 'og:') !== false ? 'property' : 'name';

	switch($name) {
		case 'custom':
			break;
		case 'title':
			if($this->titleFormat == '') break;
			$rendered .= '<title>'.$this->parseTitle($page, $content).'</title>'.PHP_EOL;
			break;
		case 'canonical':
			$rendered .= '<link rel="canonical" href="'.$content.'" />'.PHP_EOL;
			break;
		default:
			$rendered .= '<meta ' . $attributeName . '="'.$name.'" content="'.$content.'" />'.PHP_EOL;
			break;
	}
}

Also, it's a good practice to add  og:image:width and og:image:height, this ensures the image is loaded on first facebook share (otherwise it's empty). Maybe the module could automatically add these too.

  • Like 3

Share this post


Link to post
Share on other sites

I get this strange error when I try to uninstall SEO module. Anyone an idea how to uninstall the module?

Recoverable Fatal Error: Argument 1 passed to ProcessWire\Fields::___delete() must implement interface ProcessWire\Saveable, null given (line 225 of /var/www/vhosts/domain.nl/httpdocs/wire/core/Fields.php)
Edited by kongondo
The module has its own support board. Moved your post here

Share this post


Link to post
Share on other sites

Hello, 

I want to follow up with this post here as I am having the same issue. 

In my case, I am converting a wp blog over and need to keep consistent urls by (removing /blog/) from url. I am following Ryan's methodology here.. All works great, but if I automatically include the meta in the modules settings, on my post template, all of the meta is showing up twice. If I manually try to echo the seo meta, then I get the undefined index that was mentioned in the first link I referenced. 

Anyone else experienced such?

SEE BELOW  :-[

Edited by RyanJ

Share this post


Link to post
Share on other sites

Just a follow up here. The module works perfectly fine with the method above if you make sure you add the template to its settings DUH!! 

  • Like 1

Share this post


Link to post
Share on other sites

I'm getting these messages on saving the module (PW 3.023):

 Deleted field "seo_tab" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_title" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_description" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_keywords" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_canonical" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_custom" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_image" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_robots" data in 0 row(s) from 0 page(s). [page-by-page]
 Deleted field "seo_tab_END" data in 0 row(s) from 0 page(s). [page-by-page]
 Saved Module - MarkupSEO (author, sitename, imageSmart, titleFormat)

Fields are removed from allowed templates. If I manually add them back, they are gone on next save. No idea what's going on here. I completely uninstalled the module, deleted the seo-fields, but no success.

Share this post


Link to post
Share on other sites

Aside from the name vs. property issue with the Open Graph tags, it seems as though FB can be very picky about parsing og:image. It's easy to miss, because FB will infer the value based on other information on the page, but on a recent launch, in order to get it to "pass" the Open Graph Debugger, I had to add the following additional (supposedly optional) properties:

  • og:image:url
  • og:image:secure_url
  • og:image:type
  • og:image:width
  • og:image:height

It would be nice if MarkupSEO was aware of image fields and would allow users to select the preview image from one. Then it could generate all of these additional properties automatically.

 

Share this post


Link to post
Share on other sites
9 hours ago, Jason Huck said:

[...] in order to get it to "pass" the Open Graph Debugger, I had to add the following additional (supposedly optional) properties [...]

Just wanted to confirm this. I have never gone quite that far myself, but I've found out that Facebook will skip the og:image property completely unless you specify og:image:width and og:image:height with it :)

Share this post


Link to post
Share on other sites

I suspect that adding width and height is probably sufficient for non-SSL sites, but in this case, the entire site is served over SSL, which apparently made secure_url required as well, even though a secure URL was already provided for the base og:image value. I can't point to any documentation in that regard, it's just what finally worked for me.

  • Like 1

Share this post


Link to post
Share on other sites
On 3/29/2016 at 0:23 PM, Nico Knoll said:

Nope it's already in the master so you should be able to use it. If it doesn't appear in "upgrades" I'll may have to adjust the version number :)

I'm running 0.8.7 right now and it doesn't seem like you can specify on a Index, noindex, follow, nofollow etc on a page by page basis.

These setting should be showing up on the SEO tab of any page, right?

 

  • Like 1

Share this post


Link to post
Share on other sites
On 12/21/2015 at 7:54 PM, Nico Knoll said:

Have you added this to GitHub already? I know there a couple of other open issues on Github but when I find the time to work on that module I will start with the github issues :)

Hi @nico

Did you ever get a chance to look into this?

To be able to specify a NOINDEX or NOFOLLOW on a page by page basis would be great. I know the original request on GitHub is quite old but it's still a feature that IMHO would really enhance the Module.

 

  • Like 1

Share this post


Link to post
Share on other sites

Hello Everyone,

I having some trouble with this SEO module. 

I've installed this module on a site using Processwire 3.0.33 and the module is working fine. However I then installed the same module using the same method (through the Class Name) on two others sites. The first one being version 2.7.2 and the other using version 3.0.33. Both sites successfully installed the module but do not seem to be overwriting the page titles.

Does anyone know what causes this?

Thanks,

Matt

Share this post


Link to post
Share on other sites

Hi

I installed this module and it worked fine. But yesterday I upgraded the Processwire in version 3.0.44 (older was 3.0.42).

Since this action I had this error on page rendering : 

Notice: Trying to get property of non-object in /processwire/site/assets/cache/FileCompiler/site/modules/MarkupSEO/MarkupSEO.module on line 127

On line 127  : $dataRendered = $this->page->seo->render;

I lost $this->page->seo !

Any Idea ?

Thx

  • Like 1

Share this post


Link to post
Share on other sites

Hello folks,

I experienced the same issue. Once on a fresh installation with 3.0.45 and on an updated page from 3.0.44 to 3.0.45.

Both lacked the seo output support! :(

Thanks,

Martin

  • Like 1

Share this post


Link to post
Share on other sites

I'm glad you brought this up.

One of my sites visibility on Google tanked a few days / weeks ago and I finally tracked it down to this.

Since upgrading to 3.0.45 the following no longer outputs any META Tags

<?php echo $page->seo->render;?>

Keen to hear other ideas etc I'd consider this critical :(

  • Like 1

Share this post


Link to post
Share on other sites

I actually have ProCache but it was disabled when the bug appeared.

Share this post


Link to post
Share on other sites

I noticed that 3.0.42 works with this module but there is some odd-ness when

  1. ProCache is installed and enabled
  2. MarkupSEO auto injects the Google Analytics code
  3. Some minify HTML options are ticked

I'm wondering if ProCache is choking on MarkupSEOs injection of the following when it tries to minify it

<!-- Google Analytics --><script>
	(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
	(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
	m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
	})(window,document,'script','//www.google-analytics.com/analytics.js','ga');ga('create', 'UA-XXXXXX-X', 'auto');
	;
	ga('send', 'pageview');</script> <!-- End: Google Analytics -->

I can't quite pinpoint it but disabling all Minify HTML option works. 

 

Share this post


Link to post
Share on other sites

Hi all, I noticed what I think is a bug.  It seems like MarkupSEO doesn't respect the "Should page URLs end with a slash?" template setting.  I don't like having the trailing slash on the end of my urls.

I noticed MarkupSEO outputs the following:

<link rel="canonical" href="http://mywebsite.dev/support-us/donate/">

When the actual url of the page is http://mywebsite.dev/support-us/donate

 

Share this post


Link to post
Share on other sites

Hello I need to put in google-site-verification meta tag in my head but it leaves me (show on frontend) the closing tag " /> should I put this in SEO module somewhere or.

My meta looks like this.

<meta name="google-site-verification" content="<meta name="google-site-verification" content="WIERD-GOOGLE-NUMBER" />" />

How can I do this right, thank you

R

Ignore, It was wrong copy paste and pressure from a client, lol ;) Fixed!!

R

 

Share this post


Link to post
Share on other sites

Hi!

I got a little issue with this really great module:

I wan't to use the "smart description" option for a field that contains pretty lot of text.
Is there a way to shorten/strip this text down to 160 characters?
Otherwise the "smart description" make not much sense for me ...

Or is there a workaround for this issue?

Thanks!

Share this post


Link to post
Share on other sites

Sorry, i ask again.

Is there a way to avoid the modul to output the description tag, if the SEO description field is empty?
I could in this case output the shortend text of my textfield manually.

Or is there another way?

Thanks for your answers!

Share this post


Link to post
Share on other sites

I guess you could check $page->seo->description and if it's empty, set it to your likings, eg. in ready.php or in your template php file (latter untested).

if($page->seo_description === "") {
	$page->seo_description = 'whatever';
}

 

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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • 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');
×
×
  • Create New...