Leaderboard

Hey, you impatient PW users, here is a intermediate version for the current PW 3.0.17 devns branch. It is only available in the Github PW3-Tree. (you need to upload and install manually) Attention: Please first install the InputfieldRangeSlider module. It is required for the new version! The module now sits upon the new core Imagefield and provide a few more configsettings as the PW 2 version: disable enable the core image editor (default: disabled) should Imagenames be displayed by default (default: off) should Thumbnails be displayed complete, not a cropped square (default: off) style settings (color and transparency) for Thumbbackgrounds max char number for Imagebasenames (please adjust according to the length of your GridSize) (default: 15) globally disable the individual selection for Quality and Sharpening, instaed use the ImageSizerEngines defaults or define globally static defaults In the Inputfield itself, you are able to toggle displaying the Imagenames and how the Thumbnails are displayed: cover or contain. There is also a textinput for filtering by basenames. Screens:

http://jacinto-lda.com/ This is an "engine overhaul" of an existing site. Design was kept pretty much the same, but the proprietary CMS was replaced by our beloved PW, and it was made responsive, SEO and share friendly. This project prompted the ImageMarker Fieldtype & Inputfield module, coded by @Kongondo. You can see it in action in the Company / International page. Other features include a very custom vehicles catalogue. Translations are a work in progress, so some out of place portuguese is expected.

I'm not a hardcore dev either and my only encounter with Laravel was the one and only occasion when I fiddled with it for a few hours. Laravel seems to be a heavyweight campion with all those 20k+ files you need to implement even a Hello World app. Incorporating only about 1800 files, ProcessWire is definitely on the lightweight side. With its friendly community, constantly improving documentation and features I opted for ProcessWire instead of all the others I also checked out. ProcessWire sites are also easy to manage, upgrades are rarely an issue if performed with some very basic care, (say, if you modified your .htaccess, then do not replace it with the default one while upgrading, etc...). Even if you run into issues, our above mentioned friendly community is ready to help right here in the Forum

Processwire could be used for everything with it's own "Way of do things", data management or whatever you call it; but he is also beneficient and does not prohibit you to create your own parallel data structures(Like custom tables in MySQL) and make queries using PDO. In the Software House I work, we have used it even for backend in an App (iOs & Android). You just need to use your imagination.

Hi am*, Welcome to the forum, you will find that ProcessWire is called a CMF over a CMS and for very good reason, it's incredibly flexible. There is nothing you mention which stands out of the ordinary. ProcessWire has been used from everything to simple one pages to Project Management Systems, and it performs extremely well in all walks of (development) life. I would encourage you to check out the new documentation https://processwire.com/api/ref/ Updating fields such as if someone becomes a paying user, it's incredibly easy: $user->of(false); $user->addRole('member'); $user->save(); One thing to remember in ProcessWire is everything is a page, this means the API is incredibly simple not matter what you want to do, as the syntax is completely the same across all different types of pages.

Hello am*, welcome You have probably already noticed the 'Modules' section on the site. I am rather new here myself. I just wanted to point out that you will find a category of modules referred to as 'Users and Access'. I think that if you are going to be developing a site that requires user management, you will find some modules in that section that you may find very helpful in giving your development a little jumpstart. And that's only one category of modules, you will of course see the others that may contain code that you can incorporate into your site. There are tutorials to help you understand how modules are used in Processwire. You definitely want to browse through the tutorial section. Well, not just browse... you know what I mean. Get a grip on the template concept in Processwire, especially 'selectors'. Selectors are big. Anyway, I think you will be further impressed by Processwire and has others have said, this is a great community here. Very active, very helpful, very talented. Have a good day and best wishes with your site development. Oh, one last little tip for you. Actually I picked this up here from one of the threads in the forum and thanks again to the person who posted it!. You may have better results if you use Google to search the forums. Here's an example. Plug this into Google's search box ' site:https://processwire.com/talk/ user management ' Here's another that pertains to your questions ' site:https://processwire.com/talk/ table design '. Anyway, before I get too carried away and create another tl;dr type post. Enjoy!

I always think of ProcessWire as complete PHP framework bundled with integrated browser based content management tools (hundreds of tools, actually). ProcessWire should be listed here: https://en.wikipedia.org/wiki/Comparison_of_web_frameworks#PHP You do not even have to use the CMS if you don't want to, but why reinvent the wheel?

Checkout these and these lines.

Hey Pwired, thanks for taking the time to post your compliment and reply. Hope all is well in Spain. Your reply brings up more than one issue that I've been thinking about on and off for a while now. As I mentioned in my post, I'm not building sites for a living at the moment. At best I hope it is to become a part time endeavor. How realistic is that goal? I'm not too sure at the moment. I'm one of those 'old programmers' you hear about sometimes Some may laugh, and that's ok.. but I still enjoy creating software and learning new things, though I try to pick and choose wisely what I put my time into. I did spend a more than a few weeks of evenings experimenting with Wordpress after looking into it , seeing the numbers which are hard to ignore, on it's usage and popularity, etc.I was at a point where I was able to put a decent template together from scratch and I was starting to feel comfortable with the Wordpress flow. Ultimately though, I did not really enjoy working with it. It was not easy to pass on it after the time I spent on it. Sometimes you do have to invest more time than anticipated to evaluate a piece of software, especially a 'framework'. And yes I know , many don't consider Wordpress a framework or a CMS. I'm not big on semantics so forgive me ( Interesting read here on that topic if you're interested ) One of the priorities for me personally is, if I'm not enjoying what I'm working with, I'll pass on it for now. I feel much more positive about working with PW than I did with Wordpress. The code/design is MUCH easier to follow for me personally. My hat is off to Mr. Cramer and the others closely involved with development and maintenance. I'm not saying Wordpress is garbage. I'm just saying I have more respect for the internals of PW vs Wordpress. Again, not claiming to be an expert on these things, it's just my personal feeling about the matter. I would be interested, for my own benefit to see an example of what you mean by the more recent versions of PW requiring more code to accomplish a given task. Yes, I can see where a site could be put together faster with Wordpress than with PW. I would guess we're talking about relatively simple sites though? And really, who puts together a site from scratch anyway? It's not difficult to see that PW very much lends itself to creating site templates and yes it can be done with WP too, but which would be easier to implement with a satisfactory degree of flexibility? I personally feel that PW's whole Page->Template-Field concept provides great flexibility. Now I realize that WP may have plugins / themes that offer similar flexibilty. I am just not familiar with them personally. And yes, it can't be argued, Wordpress users have a huge number of plugins at their disposal and this of course might give them the edge in development speed if a similar plugin isn't available for PW. Anyway, as usual, I have rambled enough. Another fine example of tl;dr I'm afraid. Worried I might be banned from submitting posts after this. The scary part is I had more to add, but I will just save the thoughts for a post of my own sometime. Again, thank you again for taking the time to reply. On a parting note, I will only add 'Raise your rates!!' ... ( just joking.. sort of.. Have a good day.

Well I guess you have no idea how much effort is put even in simpler replies if you're not a native English speaker

You can sort multiple like this: $page->children("featured=1, sort=title, sort=timeon");

First of all thanks to Renobird and LostKobrakai for the image field upgrades. I hadn't time yet to fully try them out, but after reading the blog post I am sure, that they are a huge improvement. Especially the drag and drop function in the old image field was a little bit tedious, when sorting images. Also I know, that huge improvements like this always come with some unexpected behavior. Some of those I noticed today in my current project: I have a Repeater Matrix called content and inside this Repeater Matrix I have a repeatable item called slideshow. This repeatable item has only one regular image field called slides. Using the latest ProcessWire 3.0.17 release and its additions to the image field I notice two bugs in the UI: 1. Popover gets cut off 2. Mix-up in detail view When I switch the detail view of the images, there is always one detail view displaying two images and one of them has no details at all. Has anyone else noticed this? By the way, I am using the latest version of Chrome and couldn't see any errors inside the console. Regards, Andreas

And some actual payloads analysed here.

Plus also try https://cse.google.com/cse/publicurl?cx=014789015761400632609:fxrf0rj4wr4 for your searching needs.

Meanwhile, there's always the API reference https://processwire.com/api/ref/page/#pw-methods-languages and these dedicated multilanguage chapters / articles: https://processwire.com/api/multi-language-support/

Yes, I thought about passing the Validator entirely to JavaScript. There could be even an "on demand" mode that validates only on clicking on the panel (just an idea). Apart from the issue I had on one server Tracy loads fast here. I have PHP 7 on most servers and sometimes I get 200-250 ms speed, at least that's what Tracy shows. When I revert PHP version to 5.4 or 5.6, speed increases to 500 and 700 ms. I have to add that I use only a few panels.

No problem - thanks for clarifying and for helping to sort this out. Latest version includes that style. Let me know if there are still any problems.

This is a very beta version of the separate functions I use to generate srcset/bgset markups. There's some similar functions floating around in the forum but this one is a bit different because you can set "named image sets" which you can use easily site-wide. It's definitely work-in-progress so use it at your own risk. MarkupSrcSet Generate srcset and bgset markup for lazysizes. Features generate srcset/bgset markup for lazysizes set image sizes in JSON array add required JavaScripts automatically (optional) fallback to smallest image size if JavaScript is not available Usage Image sets JSON (in module settings): { "hero": [ [640, 210], [1080, null], [1920, null] ], "featured-image": [ [360, 240], 1.333, 2.667 ], "gallery-thumb": [ [240, 120], [480, 300], [800, 576] ] } Image methods $image->srcset(): <img <?php echo $page->featured_image->srcset('featured-image'); ?>> $image->bgset(): <div <?php echo $page->images->first()->bgset('hero'); ?>>Lorem ipsum</div> https://github.com/rolandtoth/MarkupSrcSet

-------------------------------------------------------------------------------------------------------------------------------- for PW 3.0+ please follow this link! -------------------------------------------------------------------------------------------------------------------------------- Croppable Image Module for PW >= 2.5.11 and PW <= 2.7.3 Version 0.8.3 alpha Hey, today I can announce an early (alpha) release of CroppableImage, what was forked from Anttis Thumbnails module. Until now there was a lot of work done by owzim, Martijn Geerts and me. We have solved the issues regarding the list from here: The modules are bundled together so that you only can and have to use FieldtypeCroppableImage for install, uninstall & configure. It uses new naming scheme that was introduced with PW 2.5.0 that supports suffixes. The complete image rendering is delegated to the core ImageSizer, or to any optional hooked in rendering engine. Template-settings are now fully supported, including removing variations when settings have changed. It fully respects settings for upscaling. If upscaling is set to false, you cannot select rectangles smaller than the crop setting. We implemented these enhancements: The GridView now is very nice and compact, and also benefits from the lately introduced setting for $config->adminThumbOptions. Permanent storage of the crop coordinates, quality and sharpening settings are now implemented native. No need to use PiM for this anymore. The usage/display of the Quality and Sharpening DropDown-Selects can be globally disabled/allowed in the modules Configpage. (additionally to that a setting on a 'per field base' is planned.) And the most wanted feature by the community: It gives back a pageimage and not the URL-string. This way you can use it like this: // get the first image instance of crop setting 'portrait' $image = $page->images->first()->getCrop('portrait'); You can further use every pageimage property like 'url', 'description', 'width' & 'height' with it: // get the first image instance of crop setting 'portrait' $image = $page->images->first()->getCrop('portrait'); echo "<img src='{$image->url}' alt='{$image->description}' />"; And you can proceed further image rendering with it: // get the first image instance of crop setting 'portrait' and proceed a resize with imagesizer $image = $page->images->first()->getCrop('portrait'); $thumb = $image->width(200); // or like this: $thumb = $page->images->first()->getCrop('portrait')->width(200); // and if you have installed Pia, you can use it here too: $thumb = $page->images->first()->getCrop('portrait')->crop("square=120"); The only downside with this is that when you (as the site developer) have enabled the usage of DropDown-Selects in the images editor, you do not know the values the editors have chosen for the images. As a workaround for this you can use the getCrop() method with a second param. This is a PW selector string. It can contain as many of the known pageimage options like 'quality', 'sharpening', 'cropping', etc, as you need, but none of them is required. But required is at least one setting for 'width' or 'height': $image = $page->images->first()->getCrop('portrait', "width=200"); $image = $page->images->first()->getCrop('portrait', "width=200, height=200, quality=80"); $image = $page->images->first()->getCrop('portrait', "height=400, sharpening=medium, quality=75"); . . You can get the module from GitHub: https://github.com/horst-n/CroppableImage (Better Docs are coming soon) Screenshots Related Infos A good setting in site/config.php for the AdminThumbs are: (height=>200 and scale=>0.5 !) $config->adminThumbOptions = array( 'width' => 0, 'height' => 200, 'scale' => 0.5, 'imageSizer' => array( 'upscaling' => false, 'cropping' => true, 'autoRotation' => true, 'sharpening' => 'soft', 'quality' => 90, 'suffix' => array(), ) );

Thanks to Renobird and LostKobrakai, ProcessWire’s images field has been re-designed and redeveloped with a lot of great new features we think you’ll love! This new images field is available for use now in ProcessWire 3.0.17. The linked blog post covers it in detail. There’s also a screencast at the end that shows you the new images field in action. https://processwire.com/blog/posts/major-images-field-upgrade/

You could do this in admin.php (above the line that brings in controller.php): $wire->addHookAfter('AdminTheme::getExtraMarkup', function($event) { $extras = $event->return; $extras['head'] .= '<link rel="shortcut icon" href="'.wire('config')->urls->templates.'favicon.png">'; $event->return = $extras; });

Update: Version 007 Changelog As per the request by @heldercervantes , coordinates table can now be manually sorted.

You Europeans make me smile - your English is probably better than mine Latest version comes with a few general tweaks/fixes, but the most significant are related to the Selector panel based on our recent discussions. It now returns to the "Sticky" state when you reload after a "Once" change (previously, it returned to default from the config settings). There are also now icons indicating if: the panel is set in the default list in the module config settings ("Tick" icon), the state of the panel is different for the current view, ie you have made a "Once" change (number "1" icon) In the following example, you can see that: Debug Mode is disabled. Default is enabled (checkbox icon). There is no "1" icon so it is a Sticky setting. ProcesswireInfo is disabled. Default is enabled (checkbox icon), There is a "1" icon so you know it's a "Once" only setting. Validator is enabled. Default is disabled (no checkbox icon). There is a "1" icon so you know it's a "Once" only setting. Hope that all makes sense and provides a quick visual of what the current panel settings are and what they will be when the page is reloaded.

It seems to be covered by the docs: https://processwire.com/api/selectors/#sort

Hi again. In case anyone is wondering... this module doesn't currently work with the new image field upgrade in 3.0.17 :-( As Ryan points out here https://processwire.com/blog/posts/major-images-field-upgrade Many thanks Nik

I haven't tested it this way, but I think you will be on the save side with updateting an existing site when you follow this path: If missing, install the RangeSlider module delete the whole croppableimages directory under site/modules copy the new one into site/modules, (DO NOT SIMPLY COPY IT OVER THE OLD ONE, or AT LEAST MAKE SURE THAT THE FOLLOWING FILES ARE NOT PRESENT THERE **) clear caches for modules and the file compiler update your site/config.php with the settings for adminThumbOptions (it needs at least one setting for 'gridSize', I prefer 160 over the new default of 130) open the module config page and select your setup **) have a look into site/modules/CroppableImage/InputfieldCroppableImage and delete the InputfieldCroppableImage.js and InputfieldCroppableImage.css if they exists. The PW 3 intermediate Version doesn't use this files atm. It uses InputfieldImage.js/css and InputfieldCroppableImageMan.css/js

This is SOOO cool - thank you Horst!!!!!! If the module was previously installed (old version with PW2.x) - can I just continue using it (with PW3.x) or are special steps needed/recommended now to update to the beta? (My first impression was it works right away but I am still testing.)

I think I mostly agree with you here - the downside to the current option is that requires a page reload (when you click Once or Sticky) to load the Validator panel. An AJAX option would be much quicker - you could have the panel always loaded with no content and a button to trigger the validation request. I am not really sure how much this really matters though - if you decide to do a "Once" validation and you see errors, you'll probably then "Sticky" it until you have things fixed, then "Reset". I think in the end I probably agree with you and won't worry about changing things at the moment This sounds useful - I am thinking just one icon positioned after each of the default panels so you know what is the set that is defined in the main module config settings. I would actually like your thoughts on the current behaviour regarding making some "Sticky" changes and then adding an additional panel "Once" - currently any time you do a "Once" it clears the previous "Sticky" options which I don't think it very helpful or expected. I think I will change this so that on the next reload, the states is restored to the last sticky state, rather than the default state - sound ok?

Yes, that's the same setting, see the attached image. Interesting that it doesn't work for you, here it works fine on 3.017 (just tried).

Hi. Maybe you could mix your custom research with some API calls. If you do a: $page->find() , using the field field_h_media_url as part of the selector and using the result from your custom query as value; you could access pages and modify them. Assuming you are coding from outside the main site files: foreach ($repeated_urls as $duplicate) { $repeated_pages = wire('pages')->find("template=your_template, field_h_media.field_h_media_url=$duplicate"); } Hope this could help.

Great, that´s what I wanted to hear How would you compare PW to Laravel in case of ease to use, complexity, possibilities? If there are guys here who also worked with Laravel. Of course, asking this in the PW forum will not be very represantative Are there cases where you would prefere a pure framework like laravel? I didn´t yet start developing with pw, but my feeling is that it is a bit more lightweight. What I didn´t like so much about Laravel is that it´s very much abstracted, a bit too much for me not being that much of a hardcore dev Some opinions on laravel vs pw would be interesting.

The function is a closure, which does have it's own variable scope, so local variables like $page or $user are not populated. You'd need to use one of those: wire('user') $this->user $event->user

I'm using this method for translation: https://processwire.com/talk/topic/10447-using-translatable-strings-across-template-files/ In my setup there is only 1 file '_strings.php' so PW will find translations even if it's in another file. You don't even need to include() that file, only select it in the Language Translator (admin).

Thank you very much! Now the "Panel Selector" panel looks like just the one on your screenshot and works fine. Implementing it was really cool idea, I also used to switch panels on and off a lot of by going to the PW settings, so it is a real timesaver.

Do you mean so that loads in the background so that it doesn't slow the rendering of the page itself? If so, then that sounds like a good idea. Interestingly, as I am testing the generation speed of various panels on different servers, I am seeing that almost all panels are very fast on a decent server - it seems like it is mostly my aging Macbook dev setup that is struggling - maybe I don't need to worry as much as I thought. What are you guys seeing? Thanks for looking into this - I am happy to add those styles to Tracy, but I am not sure from your message whether or not you still need those with the version I posted that includes the all: initial - can you please confirm that your code is still needed and still works on the latest version. Thanks for the kudos - glad you are loving it

New version: New config setting for the number of entries to show in log viewer panels (now defaults to 10 rather than 25 to speed things up a little). You might even want to change this to 5. The PW logs panel isn't too bad, but currently the Tracy logs panel is definitely a little slow - I will also be looking into speeding this up. Panel generation time is now listed at the bottom of each panel which should help you to decide which ones to not show by default. Unfortunately the PW Info panel is one of the slower ones at the moment, so I will tackle trying to speed that one up first. Not surprisingly, the Diagnostics and Validator panels are also relatively slow, so depending on the speed of your server, it might pay to have those off by default. Let me know if any of you notice any panels that are particularly slow on your systems.

I just installed the latest dev to see the images field changes. Some thoughts: instant previews are great d&d image replacement is useful when there's only one image added and entering edit mode, opening the lightbox and clicking on the image in the lightbox closes the lightbox but also closes the edit mode. This feels like a glitch. Clicking on "close" or on the overlay works fine though. Also, it would be nice to see these some time: viewing the file name somehow (as requested above) renaming a file for SEO purposes (as requested above) deleting all variations for an image, or maybe for all on the page. The "Variations" button could be modified to have a dropdown like the new Save buttons. the button "Crop" have other actions in the lightbox, so this could be perhaps renamed as "Edit". This would be a more appropriate naming even when adding new edit functions to the lightbox. Thanks for everyone involved, this could be a hard work with no doubt. We shouldn't expect everything working perfectly on the first iteration but it's a great start to build upon.

Well CSS is not my strongest skill, but I think this is generally tricky. There is: all: initial which has pretty good support these days, but I am still having some troubles getting initial values for everything. I have made some changes that may help you, including using proper <label> tags for the checkboxes. On an unrelated note, there is now also a toggle all checkbox for even quicker modification of panel selection. Please let me know if any of my changes helped and if not, it would be great if you could spend a little time figuring out what rules are conflicting - thanks!

Thanks for the feedback on this - I'd love to know which two panels sped things up the most - maybe I can optimize them. Thanks for reporting - I'll look into it although I am curious what styles you have that are moving the checkboxes over the labels.

In addition to @teppo and @szabesz, there are more usecases what are currently seems not to be covered well. I must admit that I first also have thought that we need the list view too. But now, after playing around a few times in the last two or three weeks (with an unofficial beta, thanks to @Lostkobrakai) I'm not even torn. I have learned to live without the listview. Usecases that are not well covered atm, for example are image rows with 20 motives that all look the same, where you need the filename, and I mean the filename of all files at once. What I come up and tested (in context of the croppableimages extension) for this are two things: one can toggle visibility of filenames over the thumbs using a little textbox for filtering by filename This is even faster than looking through an endless list of filenames. Another usecase sometimes may be to directly see the aspect ratios of all images at once, not a nice looking centered cropped square. But you will not get that WOW-effect with a visually cluttered grid, also covered with filenames all over. So IMO it depends on the usecases and the user preferences: As you also can see in the second screen, media queries are respected. This isn't what I have done, this is already in the new core imagesfield! (@szabesz: there must be a glitch somehow with your device / version) I simply have extended the new core image field and was able to use comfortable supported hooks from the core field. Here seems to be all usecases already covered on the developers side! Conclusion: with every newly introduced thing, first part is a confrontation with no more able to behave the same as before (we, the users / developers) (sorry for maybe long and bad describing words, but I think you get it) Phase two should be to find some time, play around and try out that new thing, and if you find a usecase that isn't covered well now, don't simply say we need to implement the old way here for that. I personally think I'm oldschooled in many things and also not a friend of often changing things, but I'm so happy that I have had the chance to get my hands that early to the new imagesfield and in addition also found the time to play around with it! As one result, now I have improved my own behave / workflow in some usecases and are also able to give my clients a very well looking edit page, so that they can see and say: WOW! EDIT: and sorry if it looks that I shamelessly promote the croppable extension here. The new core imagesfield from @Renobird and @Lostkobrakai allone is responsible for all the ongoing new things. I wouldn't have done anything without it and also simply wouldn't be able to do things like I now could do. This all depends on the core imagefield. Most things what I have done to adapt the croppablefield with it, was to strip out great parts from the PW2 version so that all the design and magical stuff is delegated / handled from the core imagefield.

Can you describe in more detail what worked better in old UI? I agree that there should be some nice tiled background for transparent images, but is there some other basic needs that are missing? I personally think that this is one of the "wow, that looks easy" moments for customers. Even more than before. Image fields used to take a lot of space in list view and old grid was lacking in features. Great work Tom, Benjamin and Ryan! It is also great to see more and more community effort in ProcessWire core dev!

I think creating https://laracasts.com quality tutorials but with Processwire will really help people understand the joy and power of Processwire.

I'd suggest using the WireUpload class instead of trying to emulate what it does: https://gist.github.com/somatonic/5233338 It's also best to let the file / image field move added files to the correct location and not moving them there beforehand.

What is with (Pro)-cached pages? I believe, a JS solution is needed there, as serverside PHP execution is ommitted.

I'd like to thank LostKobrakai for this excellent tutorial included in the Dec 25, 2015 blog post regarding custom page types. If you haven't read it yet, please do so. It is contributions like this by the senior members that prove selecting ProcessWire was the correct decision for this ProcessWire-Newbie. I am impressed at what I have learned within the functionality of ProcessWire, and discovering avenues I hadn't yet thought about. It is indeed a merry Christmas. I also want to thank all staff members. They deserve our gratitude for the time they dedicate to helping us learn ProcessWire, and the many avenues available with each project. For example, kongondo contribution is another great example of the team in place here. My hat is off to Ryan and his team for giving of their time and sharing their knowledge. In addition to the regular staff, there are many members, such as Kixe, Tom, (and too many others to name them all here) that also deserve recognition for their contributions and assistance. It is greatly appreciated. I am certainly looking forward to ProcessWire 2016 ;-)

Implementing this on a new site I detected a couple of "nice to haves". Sorting X and Y fields would accept decimals for fine-tuning. Bigger maps get too small for precise positioning of markers, and rounded percentage can be insuficient on the front-end. For sorting, if anyone needs it, I managed to get around to an alphabetic sorting based on the referred page's title, like this: $dots = $page->mapDots; foreach ($dots as $dot) { $dot->sortname = $pages->get($dot->info)->name; } $dots->sort('sortname'); Though it would be cool to manually sort markers on the list, this approach lets you sort by any field, and probably even the pages position relative to its real parent (I think, didn't try).

v002 is up on GitHub: https://github.com/rolandtoth/MarkupSrcSet

Thanks for this module. I use smart fields and got a little bit trouble using the description field. Because I chose fields which include html tags. Even if if I check "Strip Tags" in the field settings for seo_description. I guess that this setting doesn't take effect if the field was left blank. This results in: <meta name="og:description" content="<h2>KF Interactive GmbH</h2> <p> D-04107 Leipzig</p> <p>Tel.: +<br /> Fax: +<br /> Mail: <a href=" mailto:info@kf-interactive.com"=""> <p><strong>Konzeption und Gestaltung der Website:</strong><br> <a href=""></a> & KF Interactive</p> "> .. and breaks the layout. I changed line 206: - $pageData['description'] = $page->get(implode('|', $configData['descriptionSmart'])); + $pageData['description'] = strip_tags($page->get(implode('|', $configData['descriptionSmart']))); .. and everything works Maybe you could include this litte fix in a later version?

Version 0.7.0: Hey, I added the https option you asked for: $config->https will be set to true in runtime I guess if the template is set to use https, too. So all of the fallbacks should be covered. And I added the fix by @peterfoeng.

Version 0.6.0: Big feature: Google suggestion autocomplete Google preview updates while you type Custom contents only get sanitized now Bugfixes @NorbertH: This is not an image field because you can't have an image field in the modules config settings page. And I think this is good enough for now. Maybe I change my mind later on @toothpaste: Why no line breaks?