Nico Knoll

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

Recommended Posts

On 4/17/2018 at 7:15 AM, NoremPload said:

i cannot change the length of the seo_title field. I changed the field max length to 100 but it is still 60 at the input field. i tried to remove the counter to check, does not work. Tried to change the title and description of the field, this works. I'm confused.

Check out my fork linked to above - I think this is one of the many things I fixed. If it's still an issue, feel free to submit a PR to my fork.

Share this post


Link to post
Share on other sites

First of all, this module is great!

Unfortunately I'm having some issues. Yesterday most of the SEO data was filled in for the website. We're running a multi-lingual website, so I've changed the fieldtypes and everything worked as expected except for the homepage. For example: when I am searching the company name on google (NL), the website shows up with the link to the dutch homepage which is alright, but the seo description hasn't changed while the field isn't empty in the SEO tab on the Homepage. I can see that the meta data is in the page but google doesn't use it.

1644902634_Schermafbeelding2018-05-17om10_15_43.thumb.png.de4dfd7b3eea1242070b3dfc7596bb14.png

 Is this a known issue and can it be solved or is it something different? 

Thanks in advance!

Share this post


Link to post
Share on other sites

Hi Nico, great module.

Is there a way to use the google tag manager code instead the universal analytics code?

Thanks,

Jose G.

Share this post


Link to post
Share on other sites

I'm away next week, so don't expect any quick responses to this question, but I am curious if anyone is using my fork (don't forget to go to the other non-master branch)?

If you are, I'd love to hear your feedback and curious whether you think I should try to contact Nico and see if I can either take over this project, or whether I should make it a new module?

There are lots of new features and in my mind lots of pretty critical bug/functionality fixes.

Any thoughts?

Share this post


Link to post
Share on other sites

I could give it a try next week.

Never used this or the version from Nico so we will see.

Anything special I should look for?

  • Like 1

Share this post


Link to post
Share on other sites

Hi @adrian

I'm not using your fork actively - because I wasn't previously aware of it. I do know people who use Nico's original module - but having had a quick look at the changes in your module I'll be switching over to using it going forward. If Nico is not currently accepting pull requests, (I know I go through phases like that with my modules) then perhaps starting an alternative module from your fork would be the way to go. MarkupSEOExtended?

  • Like 1

Share this post


Link to post
Share on other sites

Hi @netcarver - thanks for your thoughts.

Nico has just given me push permissions to the repo for this module so I could now start maintaining this module moving forward.

However, I honestly don't really want another high profile module on my list of things to support at the moment, so if I do take this on, I will be looking for the community to help with PRs moving forward. Regarding your suggestion to me via PM about a community Github organization - I still think this might be a good idea, but I am also ok with being the gatekeeper for the module, just not wanting to take on being the support person - does that make sense?

The other issue is that my fork has several breaking changes that prevent easy upgrading from the current master version that is in the modules directory, so without some manual DB changes, it should only be used for new installs.

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

  • Like 3

Share this post


Link to post
Share on other sites
2 hours ago, adrian said:

Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I am yet to check out this module so I am for sure not the best person to answer this questions, however I think if you just write a short manual migration guide and prevent accidental upgrading then it should be enough for us developers.

  • Like 2

Share this post


Link to post
Share on other sites
3 hours ago, adrian said:

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I think your module fork should be on its own - just to minimize the risk to break a site.

I don't know if it's possible to check if Nicos version is installed and therefore your version can't get installed. Or similar.

If an upgrade() method is easy to do I'll be fine with it, too. 🙂 

 

Regarding community help... count me in as tester (at least as this). As we talk about testing, where is the best place to report issues? Github? Here?

 

Share this post


Link to post
Share on other sites

Thanks for your thoughts @wbmnfktr - not sure what I am going to do with it just yet, but if you feel like testing that branch in my fork, I think it's probably best to report issues on Github.

  • Like 2

Share this post


Link to post
Share on other sites
On 7/17/2018 at 6:28 PM, adrian said:

Hi @netcarver - thanks for your thoughts.

Anyone else have any thoughts on how best to proceed to ensure no-one breaks there site when upgrading to my new version? Maybe I just need to add an upgrade() method that prevents the module from updating old installs?

I'd simply call it a new version with a different fork . Put a notice on the current version that a new version is available.

Perhaps a user like me can have V1 installed and then simply install separately install V2, test and then remove V1.

Share this post


Link to post
Share on other sites

I’d love to see, as an option, a user-supplied character inserted between title and sitename. For instance, I usually use the pipe (|) character or sometimes a hyphen. And this character would only obviously be inserted if both title and sitename are used. If sitename isn't supplied, then the pipe or whatever gets stripped.

  • Like 1

Share this post


Link to post
Share on other sites
On 5/17/2018 at 10:17 AM, Harmen said:

First of all, this module is great!

Unfortunately I'm having some issues. Yesterday most of the SEO data was filled in for the website. We're running a multi-lingual website, so I've changed the fieldtypes and everything worked as expected except for the homepage. For example: when I am searching the company name on google (NL), the website shows up with the link to the dutch homepage which is alright, but the seo description hasn't changed while the field isn't empty in the SEO tab on the Homepage. I can see that the meta data is in the page but google doesn't use it.

1644902634_Schermafbeelding2018-05-17om10_15_43.thumb.png.de4dfd7b3eea1242070b3dfc7596bb14.png

 Is this a known issue and can it be solved or is it something different? 

Thanks in advance!

Was this solved? Im having the same issue. Everything looks fine but the home page SEO won't update. Even if I post link through Facebook. All othes pages and suppages work fine. Looking through source all is there and looks fine. Any ideas?

Thank you

R

Share this post


Link to post
Share on other sites

Hi everyone,

I read a few things about implementing a multi-language feature of this module but I can't find anything in the module.
Has anyone managed to do a multi-language setup with SEO?

Also the meta tags are in the source file but Google doesn't use them.
Same issue as @Roych

 

Share this post


Link to post
Share on other sites

For multi-language SEO tags you can use a FieldtypeFieldsetGroup in your templates (put it on a new tab for easy access):  https://processwire.com/blog/posts/processwire-3.0.73-and-new-fieldset-types/ .. echo this vars inside an included file (or use a Markup Region) in the main template file.

PS: I never try with FieldtypeFieldsetPage, but can works too

  • Like 1

Share this post


Link to post
Share on other sites
37 minutes ago, joelplambeck said:

Hi everyone,

I read a few things about implementing a multi-language feature of this module but I can't find anything in the module.
Has anyone managed to do a multi-language setup with SEO?

Also the meta tags are in the source file but Google doesn't use them.
Same issue as @Roych

 

If you have the required language modules installed, you just change the field type of the seo fields, look for field seo_title, and see that you can change it to other types of fields, in this case, you want Text multilanguage for seo_title, it should show up after the multilanguage modules are setup. 

  • Like 2

Share this post


Link to post
Share on other sites
2 minutes ago, elabx said:

If you have the required language modules installed, you just change the field type of the seo fields, look for field seo_title, and see that you can change it to other types of fields, in this case, you want Text multilanguage for seo_title, it should show up after the multilanguage modules are setup. 

Oh wow, Thank you so much @elabx 

I could have come up with that myself. Sometimes you don't think of the easiest solution. Thanks for giving me a heads up!

You have a great day!

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 blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • By BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/