Jump to content
Nico Knoll

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

Recommended Posts

You at the wrong place.

explanation see line:

https://github.com/NicoKnoll/MarkupSEO/blob/master/MarkupSEO.module#L417

you've changed the fieldname in the module settings page.

change the <meta> tag itself could be done in this line:

https://github.com/NicoKnoll/MarkupSEO/blob/master/MarkupSEO.module#L340

for real dublin core metas this module should get an option for this with a checkbox - to add the DC. tag to every meta tag and add additional tag like content type or created date.... could be done with a checkbox in the settings and an additional if statement to get those DC.tags.

May Nico find some time, if i've got more time on my hands i would proud to contribute to this awesome module...but my calendar says :frantics:

Best regards mr-fan

  • Like 1

Share this post


Link to post
Share on other sites

btw in the new dublin core spec you don't need to capitalize DC

Share this post


Link to post
Share on other sites

Therefore it will not help for adapting a single Tab. But, the single entry (description) <meta name="description" is defined somewhere. Exist to the module additional files, which may not be in the module directory? Somewhere, the entry must be ...

Share this post


Link to post
Share on other sites

Alternative to changing the module itself is to render the stuff yourself...so you've full control over the output meta tags

like Nico wrotes:

$page->seo // includes all the default values mixed with the page related seo data

// e.g.:
$page->seo->title
$page->seo->keywords

// for rendering all fields with the module
$page->seo->render

//example with DC and own markup
echo '<meta name="DC.descritption">'.$page->seo->description.'/>';

so the tags are up to you in your frontend template.

May the best solution if you don't wanna change and maintain module files.

regards mr-fan

  • Like 1

Share this post


Link to post
Share on other sites

First off, thank you for this great module.

I have installed the latest version (0.8.2) and assigned one template (workshop)

I'm doing import of pages from a Joomla site and want to set values for SEO fields through the API.

But I get this message when trying to save data to SEO fields:

"Notice: Indirect modification of overloaded property Page::$seo has no effect in /var/www/qgtpw/site/templates/convert.php on line 225".

My code

$data = csv_to_array('inc/joomla_workshops.csv');

foreach($data as $csv) {
	$jid = $csv['id'];
	$title = $csv["title"]; 
	$description = $csv["metadesc"];
	$keywords = $csv["metakey"];
	$workshop = $pages->get("template=workshop, jid={$jid}, include=all");
	if ($workshop->id) {
		$workshop->of(false);
		var_dump($workshop->seo);

		if ($title != "") $workshop->seo->title = $title;
		if ($description != "") $workshop->seo->description = $description;
		if ($keywords != "") $workshop->seo->keywords = $keywords;

		$workshop->save();
		$wokshop->of(true);
		echo "$jid<br>";
	}
}

The var_dump gives "null";

How would I go about saving data to the SEO fields via the API?

Share this post


Link to post
Share on other sites

Gebeer you could try to set them - i do that with a custom script to get seo fields prefilled on publishing if users don't fill seo fields manually.

example:

//set seo_title on publishing
$page->set ('seo_keywords', $default_keywords);

//set seo_description on publishing
$page->set ('seo_description', $default_desc);
...

set should work for you.

best regards mr-fan

  • Like 4

Share this post


Link to post
Share on other sites

@mr-fan

Thanks a lot. This is working perfectly :)

  • Like 1

Share this post


Link to post
Share on other sites

@ceberlin:

Select a custom field with a fallback to title?

You can use multiple smart titles. So the first one will be used if filled (https://github.com/NicoKnoll/MarkupSEO/blob/master/MarkupSEO.module#L182-L187). If not the second one is used and so on. "Smart title" will be used in case you leave the "Title" field in the SEO tab empty.

Bildschirmfoto%202015-01-24%20um%2015.09

I might be missing the obvious here but I can't find anywhere to configure the smartfields as shown in that image. I am using the latest version of the plugin, and the config page doesn't have anything for smartfields.

Thanks for the great work!

Share this post


Link to post
Share on other sites

Uncheck "Use parent's values if empty?" and a whole new world appears.

  • Like 1

Share this post


Link to post
Share on other sites

Uncheck "Use parent's values if empty?" and a whole new world appears.

Wow, I thought exactly the opposite, that I had to keep that option checked!  :undecided:

Thanks!  :-[

  • Like 1

Share this post


Link to post
Share on other sites

I really like your Module. But it worked only about 15minutes for me. After inserting Text to several pages I got:

Notice: Undefined index: canonical in /site/modules/MarkupSEO/MarkupSEO.module on line 250

Notice: Undefined index: title in /site/modules/MarkupSEO/MarkupSEO.module on line 266

Notice: Undefined index: description in /site/modules/MarkupSEO/MarkupSEO.module on line 268

Notice: Undefined index: image in /site/modules/MarkupSEO/MarkupSEO.module on line 270

Notice: Undefined index: title in /site/modules/MarkupSEO/MarkupSEO.module on line 277

Notice: Undefined index: description in /site/modules/MarkupSEO/MarkupSEO.module on line 279

Notice: Undefined index: image in /site/modules/MarkupSEO/MarkupSEO.module on line 280

Notice: Undefined index: custom in /site/modules/MarkupSEO/MarkupSEO.module on line 28

I have no idea whats the problem. Also deleting an reinstall of the Module doesnt solves the problem. All fields are recreated and empty. Still throws that errors. I am using the latest Version 0.8.2.

Share this post


Link to post
Share on other sites

Those php notices shouldn't prevent the module from working. Admittedly they should be fixed, but are you sure that the module is no longer working? If you disable debug mode you shouldn't see the errors.

Share this post


Link to post
Share on other sites

All SEO Tabs disappeared from Pages and there is no output anymore. Also all my inputs Ive done are not accessible anymore.

I can reconfigure everything and manually add all fields to each template and place them in a own SEO-Tab. But this would be nearly the same way, as I created my own SEO-Tabs in the past. Means there are no advantages of the module anymore. Because I have to trust in the abilities of this module. If its not working properly my project would be harmed. So better I take the safe way. 

Would be great if there is any solution. Cause the features of this module are really exciting and would help a lot.

Share this post


Link to post
Share on other sites

Just a small feature request.

Any chance of added an option to do Enhanced Link Attribution?

All it requires is an additional line of code to the Google Analytics code that is already generated (highlighted in Red)

I will probably modify my local MarkupSEO module code for now but it would be great to see it as part of the official code branch.

P/S I'm a fan of the module. Would happy to buy some beers to show my appreciation.

ga('create', 'UA-XXXX-X');
ga('require', 'linkid', 'linkid.js');
ga('send', 'pageview');
 

  • Like 1

Share this post


Link to post
Share on other sites

I've just noticed that removing the GA Code from MarkupSEO and saving the settings results in all the SEO data previously entered being deleted.

Is this by design, or more likely a bug?

Luckily, we bulk upload our SEO settings via Spreadsheet/PW Custom code so it was easy to restore the values.

I've had several of these messages logged for the different SEO fields

"Deleted field "seo_tab_END" data in 0 row(s) from 0 page(s). [page-by-page]"

Share this post


Link to post
Share on other sites

I really like the ease of use of this module. I'm using it on a page which I'm working on and seems to be pretty good for google searches.

But I have one issue...

I would like to have the page I'm working on in google searches listed as this:

Main site
    child page 1   child page 2
    child page 3   child page 4
    child page 5   child page 6
    child page 7   child page 8

as only one google search listing. Right now I get every page separately in the google search, making it look little messy. This might not be due to this plugin but google settings but I'm not sure. Anybody knows what I should work on to get it working?

  • Like 1

Share this post


Link to post
Share on other sites

@Olli: It's explained here: https://support.google.com/webmasters/answer/47334?hl=en

So I guess the module has no real impact on that. But try to add a sitemap and with a bit of luck Google will find fitting sitelinks


Just a small feature request.

Any chance of added an option to do Enhanced Link Attribution?

All it requires is an additional line of code to the Google Analytics code that is already generated (highlighted in Red)

I will probably modify my local MarkupSEO module code for now but it would be great to see it as part of the official code branch.

P/S I'm a fan of the module. Would happy to buy some beers to show my appreciation.

ga('create', 'UA-XXXX-X');
ga('require', 'linkid', 'linkid.js');
ga('send', 'pageview');
 

Hey, 

I'm glad that you like that module. Could you add any bugs directly on GitHub?

(And I'm always happy if someone is buying me beer ;) (There is a link under this text - just saying ;) ))

Share this post


Link to post
Share on other sites

I may have missed this, but is there any way to override a value at runtime, prior to calling ->render?

I'd like to programmatically insert a page-specific value for og:image, something like:

$page->seo->{"og:image"} = '/path/to/image';
$page->seo->render;

Any way to do something like that?

Thanks!

Jason

Share this post


Link to post
Share on other sites

Is it possible to reassign field values from within a template? Not save back to the database, just override in memory.

I'm using the MarkupSEO module, and want to use its built-in ->render function, but I want to tweak some values first, e.g.:

$page->seo->{"og:image"} = '/path/to/image.png';

$page->seo->render;

Possible?

Share this post


Link to post
Share on other sites

I'd say it's not without modifying the module. $page->seo is an raw data object, where render is not actually a function, but already the prerendered result of the rendering logic.

Share this post


Link to post
Share on other sites

Mod Note:

@Jason,

Please try not to double post. You asked the same question earlier today :-). Merging this thread with MarkupSEO's support forum since your question is really about that module.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry for the cross-post, wasn't sure if my question was module-specific or more of a general api question.

Sounds like the answer is "no", since ->render is pre-rendered.

Thanks!

Share this post


Link to post
Share on other sites

No worries.

As for general API, yes you can override (and even create methods and properties) on the fly at runtime since PW is an OOP application. So (and I assume you probably know this) you can do:

// where such a field does not exist (i.e. this page has no summary field but we create one at rt)
$page->summary = 'My nice summary';
// and you can also do, replacing the saved page title at rt (but not saving it)
$page->title = 'My replacement Title'; 
Edited by kongondo

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...