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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild.  
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Steps (Read more) Manual override of the selected value (will still adhere to the rules above) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant If it's usable for others I'll add it to the Modules list  
      Changelog
      v002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional 
      v001
      - Initial release
       
      Thanks!
       
       
    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

×
×
  • Create New...