Wanze

Hi folks, I just released version 1.1.1 which fixes the PHP 8.1 related errors from this issue: https://github.com/wanze/SeoMaestro/issues/41 These issues have been fixed by merging a pull request. I appreciate if the community can help me out, as I am quite disconnected from the ProcessWire world (as you might have noticed). However, I still want to support this module with bugfix releases. Cheers

Hi @Flashmaster82 In this case you need to use the module "WirePDF" bundled in the Pages2Pdf module. You can use WirePDF to generate PDFs with custom content and styling. The readme has some examples how to do this: https://github.com/wanze/Pages2Pdf#wirepdf I suggest to also take a look at other existing ProcessWire PDF modules, as this one is really old and not maintained actively - it still works though ? Cheers

The module uses an object "PageFieldValue" which holds the hydrated data from the database and gets initialized by the fieldtype: https://github.com/wanze/SeoMaestro/blob/master/src/PageFieldValue.php Each meta data group has its own class to render specific data, e.g. this one for the "meta" group: https://github.com/wanze/SeoMaestro/blob/master/src/MetaSeoData.php Hope that helps a bit ?

Hi @Andoro From your description it sounds like you have a memory problem. Do you see anything in the logs? Try bumping your "memory_limit" setting in your php.ini file, does it help? Cheers

I would have to look how ProcessWire handles this case, not sure if it's easily doable. Currently, I don't have time available, if you'd like to take a look - I'm happy to merge a pull request ? Cheers

You can setup the default values for each template and pages using that template will inherit the configured placeholder by default, unless overridden on page-level. For your second question: No, there is no such fallback implemented. You would need to programmatically add that logic yourself by using hooks.

Hi @iNoize It should work, here's a quote from the readme: However, you can only use one field as placeholder for the Opengraph image, so either {images} or {immo_images}. Hope that helps! Cheers

Hi @csaggo.com It seems like there is no url field for opengraph tags. At the moment, the og url is generated dynamically based on the page's httpUrl, so you cannot change it at runtime. If the module would use the canonical url at render time, it should work. Can you open an issue on GitHub? ? Cheers

Hi @3fingers Yes and no ? I used ProcessWire for some projects as freelancer, but never at my "daily" work. I still believe that ProcessWire is a great open source software and I'm maintaining a couple of private projects. But in my opinion, ProcessWire lacks of some important features (testing, config management, migration handling, command line tools, extensible frontend etc.) and also it is not easy to setup if multiple people are working on the same project. Nowadays I am writing Flutter apps and Javascript. But of course I still come back here to give some support and to see how ProcessWire evolves! ? Cheers

You're welcome! ?Let me know if you need any help in implementing a solution using hooks. Maybe the following examples from the tests could be useful : https://github.com/wanze/SeoMaestro/blob/master/tests/src/SitemapManagerTest.php#L177-L220 Cheers

You have the following possibilities: Manually include/exclude all pages via SeoMaestro field Setup the default value on template level to not include pages in the sitemap, and then manually include them via SeoMaestro field. Or vice versa, whatever makes more sense ? If you know how to use hooks: Exclude the hidden pages by using the hook mentioned in my first answer Cheers

Hi @B3ta, The sitemap generation should not affect your frontend; the sitemap should only be generated on requests where a user is logged into the admin: https://github.com/wanze/SeoMaestro/blob/master/SeoMaestro.module.php#L154 1. If the performance is a problem on sites with a large amount of pages, I suggest to disable the automatic generation and to create the sitemap manually via cronjobs. You'd need a CLI script that bootstraps ProcessWire and then executes $wire->module('SeoMaestro')->getSitemapManager()->generate(). 2. I would be happy to support multiple sitemaps, but I do not have any time/capacity at the moment, nor am I working with ProcessWire anymore. If anyone would like to contribute this, please send a pull request! Cheers

Hi @HerTha, What kind of control do you need exactly? Hidden pages are not excluded from the sitemap by default. Currently, you can either include/exclude hidden pages via SeoMaestro field. Or you can use the following hook to alter sitemap items programatically: https://github.com/wanze/SeoMaestro#___sitemapitems Cheers

Hi @palacios000 There is no setting to strip HTML tags, you'd need to use the following hook to transform the value prior to being rendered by the module: https://github.com/wanze/SeoMaestro#___renderseodatavalue Cheers

@Ben Sayers Are you trying to search meta data in a SeoMaestro field? Unfortunately this is not possible due to the data structure being used by the module, see: https://github.com/wanze/SeoMaestro#available-selectors Cheers