Nico Knoll

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

@peter: I think I merged a pul request regarding this topic: https://github.com/NicoKnoll/MarkupSEO/commit/b51893486631a980ed33bbc451dcfc3d1105a329

@guy verville: Have you tried using smart-fields for it?

Well I'm using Bootstrap Grid without all the other Bootstrap stuff. works quite nice and easy to adopt for people who have bootstrap experience

@pete: I'll have holidays at university in around a month and gonna tackle all open issues with the module from GitHub. So thanks for finding it - could you add it at GitHub as well so I won't forget it?

Really cool. Would love to see this in the PW 3.0 final build (at latest) if possible

@peter: Good question. Haven't worked on the module for a long time now as I had a lot to do recently. 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

Nice animation  

@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 ))

Do you replace double spaces afterwards to? Because a lot of people tend to make a space and than press enter (or Word does this and they just copy and paste it)

An maybe you could add a "maxlength" option and do a "nice break" so the last word won't be cut (as explained here: http://stackoverflow.com/questions/79960/how-to-truncate-a-string-in-php-to-the-word-closest-to-a-certain-number-of-chara).

This would make sense because meta tags have a length restriction I think.

Here is PIWIK's blacklist: https://raw.githubusercontent.com/piwik/referrer-spam-blacklist/master/spammers.txt

Well I think it makes sense. Take the date field for example. You define an input and an output format. But "input format" means how it is displayed in the backend - not how you really put data into it. "Output format" means how it is outputted if you call $page->datefield;

If you call "$page->datefield" you don't get the real field but the formatted output (a string) by a runtime formatter. But the field itself does not know how it's output looks like. So If you try to overwrite it the field will not know how to interpret. But if you disable of first the value you get/set is the "real" value of the field.

So just try to keep in mind to disable of before editing a page/saving fields

Really nice

@guenther55: Go to the settings page and select the templates that should get seo fields

Well 

<?php echo wire('page')->seo->render; ?>

or 

<?php

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

are the way to go. 

In your settings you can either enable automatically insertion of the meta fields (so you dont need to do this) or you can enable "manual" and then you will need this code (or you're rendering the tags in some other way)

@peter: Good idea but at the moment it only supports title and sitename.

So you have to leave that field empty and do it manually as explained above: https://processwire.com/talk/topic/8007-markupseo-the-all-in-one-seo-solution-for-processwire/?p=85640

Hey,

a lot of times I create a role called "editor" and give all of the page-* permissions to it. No problems so far. But I normally forget to go to "home" template afterwards to set the permissions for the template, too. So my idea is to show a list of templates (maybe only the once you have selected as "Manage access individually") in a list like the following in the role edit screen:

I think this would be a huge performance improvement and could save a lot of confusion and clicks.

@rick: If any question should appear while you're (hopefully) do your projects in the next days just come back to the forum and ask - we're happy to help you here (And welcome to the ProcessWire family of course  )

Fixed

Hey,

what I really would like to have are "virtual templates". It's already possible if you create a template via api but not via the admin backend.

What is a "virtual template"?

A virtual template is a template using a fieldset of an other template. So you can't define fields for it but you can create special template files instead of building a switch function into your template file.

For example:

For example you have a "grid" template which contains an image field and two textfields. Now you want to have a grid-sport and a grid-food gallery. But you want to have different appearances for them even if they need the same fieldset.

Shouldn't be hard to implement and could make a handy addition

Hey,

I think it's time to remove "templates-admin". In my opinion the shared functionalities which are still used by Reno and Default Admin Theme should be put in a separate plugin ("AdminTheme") or a core class ("AdminTheme.php") and the old "templates-admin" should be removed.

To prevent that No admin theme is installed there should be a check if you try to uninstall an AdminTheme. And AdminThemeReno shouldn't have DefaultAdminTheme as dependency anymore but only "AdminTheme" class. 

This just makes more sense in my mind and prevents questions like this (which are completely understandable): https://processwire.com/talk/topic/10329-why-admin-theme-is-in-2-folders/ and questions about the old theme randomly popping up.

As Ryan wants ProcessWire to be usable without AdminTheme, too, it's probably the better way to put the stuff in a module (as mentioned above) which can't be uninstalled (unless you know how to force uninstall modules).

Please put this on the list for 2.7...

Thanks,

Nico 

And I'm not sure if "allow field-specific skins" is possible with CKEditor as it doesn't use iframes but loads the js at the top. So the skin of the last loaded editor is used I think.

Source: http://stackoverflow.com/questions/30481246/ckeditor-multiple-skins-on-a-single-page

Btw.: You can set it globally if you just go to /site/modules/InutfieldCKEditor/config.js and add it there like this:

CKEDITOR.editorConfig = function( config ) {
    config.skin = "lightwire,/site/modules/EditorSkinLightwire/skins/lightwire/";
};

I think that solves it. I'm going to add this to the description.

Call me Captain Hook as I can hook into almost everything - at least I'll try this

If you need an easy start for your development try: http://modules.pw