Mike Rockett

Bumped to 0.1.2-beta Fixed descriptions to better explain the purpose of the fields added to templates. If additional non-related fields are ever added, these descriptions will be amended accordingly. Removes sitemap cache on module-save. This is already done when pages are saved, unless the option in MarkupCache's config dictates otherwise.

Hi Mel, You're most welcome. The list on the configuration page defines templates which get the sitemap_ignore_page and sitemap_ignore_children fields. As the home page should not be ignored, the home template does not get the fields (the module would be pretty much useless otherwise). The presentation of the sitemap works out of the box without any configuration. Edit: I think the module config should be a little clearer with the explanation. I will sort that out now. The sitemap should be working at that URI. If you're looking for a simple sitemap, maybe use MarkupSitemapXML and see if it renders. If it does, then it means I've done something wrong with my module, which is based on that one.

Agreed. I'm still convinced that PW should be PHP 5.6+ as everything before that it unsupported (all support for previous versions ended over a year ago). At the very earliest, I think the limit should be 5.5. Edit: I actually think Teppo should run a weekly.pw poll on this...

There are other files that use the new array syntax, so those would need to be changed too. Considering that changes would need to be made to vendor libs as well, the best bet would be to get onto a newer version of PHP.

Ah right, didn't actually think it was a config property (wasn't looking properly).

Yes, that means you're on PHP < 5.4. Highly recommended to upgrade to 5.6 at the very least.

Bumped to 0.1.1-beta Added image support: You can now specify fields in module config that should be included when rendering the sitemap. Simply choose one or more image fields from the list, and any Page that uses those fields will have their images listed in the sitemap. If a description is present, it will be used as the image caption. Also supports ImageExtra. To add specific details to your sitemap's image entries, use ImageExtra to add the meta fields accordingly: Add a license field to set a license for the image (it must be a URL, or it won't be included) Add a title, if needed Add geo, location, or geolocation if you'd like to specify the geo-location of your images The template field in ModuleConfig was changed from includeTemplates to sitemap_include_templates. The ModuleConfig fields now show template and field labels, and not their names. Small changes to the per-Page config field descriptions and labels

@kongondo Thanks! Works like a charm now.

Docs & Download: rockettpw/seo/markup-sitemap Modules Directory: MarkupSitemap Composer: rockett/sitemap ⚠️ NEW MAINTAINER NEEDED: Sitemap is in need of developer to take over the project. There are a few minor issues with it, but for the most part, most scenarios, it works, and it works well. However, I'm unable to commit to further development, and would appreciate it if someone could take it over. If you're interested, please send me a private message and we can take it from there. MarkupSitemap is essentially an upgrade to MarkupSitemapXML by Pete. It adds multi-language support using the built-in LanguageSupportPageNames. Where multi-language pages are available, they are added to the sitemap by means of an alternate link in that page's <url>. Support for listing images in the sitemap on a page-by-page basis and using a sitemap stylesheet are also added. Example when using the built-in multi-language profile: <url> <loc>http://domain.local/about/</loc> <lastmod>2017-08-27T16:16:32+02:00</lastmod> <xhtml:link rel="alternate" hreflang="en" href="http://domain.local/en/about/"/> <xhtml:link rel="alternate" hreflang="de" href="http://domain.local/de/uber/"/> <xhtml:link rel="alternate" hreflang="fi" href="http://domain.local/fi/tietoja/"/> </url> It also uses a locally maintained fork of a sitemap package by Matthew Davies that assists in automating the process. The doesn't use the same sitemap_ignore field available in MarkupSitemapXML. Rather, it renders sitemap options fields in a Page's Settings tab. One of the fields is for excluding a Page from the sitemap, and another is for excluding its children. You can assign which templates get these config fields in the module's configuration (much like you would with MarkupSEO). Note that the two exclusion options are mutually exclusive at this point as there may be cases where you don't want to show a parent page, but only its children. Whilst unorthodox, I'm leaving the flexibility there. (The home page cannot be excluded from the sitemap, so the applicable exclusion fields won't be available there.) As of December 2017, you can also exclude templates from sitemap access altogether, whilst retaining their settings if previously configured. Sitemap also allows you to include images for each page at the template level, and you can disable image output at the page level. The module allows you to set the priority on a per-page basis (it's optional and will not be included if not set). Lastly, a stylesheet option has also been added. You can use the default one (enabled by default), or set your own. Note that if the module is uninstalled, any saved data on a per-page basis is removed. The same thing happens for a specific page when it is deleted after having been trashed.

I thought that may be the case -- thanks! And thanks for the explanation, I understand how it works now.

Thank you! It does appear to work, but the root page is also assigned the current class when viewing any decsendant. This is my code: $view->siteNavigation = $menuBuilder->render('site-navigation', [ 'current_class' => 'here', 'menu_css_class' => 'menu-items', 'default_class' => 'menu-item', 'current_class_level' => 0, ]); And this is the output: <ul class="menu-items"> <li class="menu-item here"> <a href='/'>Home</a> </li> <li class="menu-item"> <a href='/about'>About</a> </li> <li class="menu-item"> <a href='/security'>Security</a> </li> <li class="menu-item"> <a href='/recycling-initiatives'>Recycling</a> </li> <li class="menu-item here"> <a href='/newsroom/'>Newsroom</a> </li> <li class="menu-item"> <a href='/contact-us'>Contact Us</a> </li> </ul> Is there no clean way to add an option to specific menu items that states "add current class here if an included / non-included descendant is current"?

In normal situations, apps that run as the administrator can write to the hosts file. Sometimes, Antivirus does this nonsense of locking the file, and then they don't provide a simple option to unlock the file for writing. Glad it's all working now.

I've faced the same issue, and landed up changing the domain extension to .local instead of .dev due to the ICANN name collision. It's been working like a dream so far. Note that, if you do this, you will need to manually edit your hosts file, as well as your Apache vhosts (shortcuts to all of these are available in the system tray menu) for existing sites.

Glad it worked out for you. Laragon has replaced XAMPP and EasyPHP (in that order) as it's the only thing that works well for me. What's even better is one can add a "Quick Create" profile for ProcessWire, just by pointing to the latest ZIP release on GH. In the configuration option, add: # ProcessWire ProcessWire=https://github.com/processwire/processwire/archive/master.zip Done!

That is a gorgeous website by the way. Love it.

No problem at all -- I'm sure you're quite a busy-bee. Thank you, looking forward to testing it.

Hi Margie, I really wish I knew of some big government sites powered by PW, though I can make an assumption as to why there many not be any, and it's exactly as you say it: big name systems tend to come first (I guess people are fearful of jumping into the unknown). I'd imagine that many of them use Drupal or maybe even SiteCore (I think it's that one, not sure). It would've been so much nicer if those above could delegate properly, and know full-well in advance that no matter what system is used, it would be used well because it would've been vetted properly (trust issues, perhaps?). That aside, hopefully there are some sites that folks know of and that it helps point the project in the right direction (nudge nudge).

I'd suggest the full package of Laragon. Comes with the usual AMP stack and a bunch of utilities that mike life easy. If you're happy with your existing stack, then maybe use Scoop, which is like Homebrew for Windows. Either way, git will become available in your path and your IDE can use it. I wrote a short post on Scoop some time back: https://blog.rockett.pw/post/scoop

There are a couple of things that can shine out above all else. One of these things is cost-reduction. I've often said to my clients that using ProcessWire over WordPress is farmore cost efficient due to its simple flexibility. Naturally, this depends on the client and their needs, but, at the end of the day, putting together a site with PW is easier and far more straight-forward, and this needs to be communicated to the client. Unfortunately, I don't use WordPress at all, and so I don't have any statistics for you. What you really need to do is take all the known considerations and put them into context. Present it as a document, and you can win the client over. I'm surprised the WP=CMS mentality still exists...

The most recent 0.8.0 exists on GH again: https://github.com/mikerockett/SimpleForms. Will bump to 0.9 soon after a few modifications have been made. With form building, I'm thinking of making use of the AbvFormBuilder method, but not sure yet. Still need to investigate how it all works.

That's quite nice... Will think on it. ?

Wanted to continue developing this today, but it appears I've lost the latest source for it. After removing it from GH (can't remember why I did that), I kept a local copy and can't seem to locate it. Will continue looking and re-commit to GH. I don't want to call it RockettForms anymore (I know we voted). As the module is dev-centric, I'd like to use an apt name, like DevForms or something. Not keen on keeping it as SimpleForms due to possible confusion between Simple Contact Form. Will update you all when I find the source (it has to be somewhere, right? ?). Update: I appear to have found it! Will need to do some work on it before I commit a newer version.

All resolved -- using the PW3 branch now. Thanks for the help.

I'm beginning to think you're using a different release or something... This is my controller now: $leaflet = $modules->MarkupLeafletMap; $view->mapHead = $leaflet->getLeafletMapHeaderLines(false); $view->map = $leaflet->render($page, 'map', [ 'height' => '500px', 'scrollWheelZoom' => false, ]); And this is the output: $(function() { var mleafletmap1 = new jsMarkupLeafletMap(); mleafletmap1.setOption('zoom', 14); mleafletmap1.init('mleafletmap1', -26.172777, 28.085833, 'CartoDB.Positron'); var default_marker_icon = L.AwesomeMarkers.icon({ icon: 'home', iconColor: 'white', prefix: 'fa', markerColor: 'darkblue' }); mleafletmap1.addMarkerIcon(default_marker_icon, -26.172777, 28.085833, '/contact-us', 'Contact Us', ''); }); There's nothing in MarkupLeafletMap.module that indicates the options I provide should be added, unless I'm adding multiple markers, in which case it adds to relevant addMarkerIcon function-call to the script. I could well set the two options require in init, but that's not the correct solution.

That's exactly what I need it to do, but it doesn't add the relevant option to the JS code... Let me investigate.