Stefanowitsch

hi @Roych! I have a question: Right now the file size of the pages database is growing and growing since all analytics data is saved here. Is it possible to configure the save duration of the analytics data that is saved here to prevent the database from growing too large?

I still use the less file watcher method in my IDE (PhpStorm) because of this 🙂

Oh I see four options and have to make a decision? 😄 Well, for me personally option A or option D are the best. I would say that option D is even better! But that depends on the user and the use case. Since I don't use the embed video feature at all I have no need for this stylesheet at the moment.

Hi Peter! I just discovered (I am using 1.1.950) that there is a css file that is loaded in the frontend of my page: /site/modules/MediaHub/assets/css/media-hub-rte-content.css By looking into this file its seems the styles are used for embedding elements: /** * MediaHub — RTE image alignment + YouTube/Vimeo embed wrappers. * * Loaded on the live site and inside TinyMCE via content_css (see MediaHub.module.php). * Class names match ProcessWire ProcessPageEditImageSelect defaults. */ Is there an option to disable the loading of this file?

hi @maximus I have a question: currently it seems that when a description text is taken from a body field on a page the included html markup is inserted, too. This happens in the schema markup and the meta description. For example, the <p> tags are included here: { "@type": "BlogPosting", "description": "<p>Der Förder-Dschungel nervt, aber wir bringen Ordnung rein. Wichtigste Änderung: Das BAFA macht keine einzelnen Heizungen mehr, sondern nur noch…" } And another question: I want to render different schema.org markups for different page templates. In the module settings page I pasted this markup inside the "template defauls JSON" field: { "basic-page": { "schema_type": "WebPage" }, "news-entry": { "schema_type": "BlogPosting" } } It does have no effect as it seems. The BlogPosting markup is never applied to any pages that use the "news-entry" template. This works only if I select this particular schema setting in the schema tab when editing a page:

Hi @eutervogel! I am extremely surprised and impressed. This shop "module" basically came out of nowhere and solves a huge "black hole" in the ProcessWire community: A functional, up-to date and all-in-one shop solution. I made a shop with Padloper (Version 1) years ago which was one of my first PW projects ever. And in my main job I am working for one of germanys biggest e-commerce shops. Coming that way I now what immense work setting up, developing and not least maintaining an online shop is nowadays. You have tons or regularities that you have to take care of and each year something is added. For example: Last year all bigger online shops had to be be overworked due to the German Accessibility Improvement Act now the latest "addition" was the integration of the "electronic cancellation button". If you offer a shop solution for a client based on an existing system or "custom made" - you have to be in constant awareness of the legal changes and act immediately. Then you have to design the landing page, category pages, product pages, the checkout pages, search pages and the whole customer backend. Not to mention many many e-mail templates. Because of that the last shop that I set up for a client was actually a Shopify solution. That still was a ton of work, especially if you consider the countless hours for reading the developer docs and becoming familiar with the Shopify CLI and the whole template/development system (and so on!). So it's nice to see that there is a PW alternative now. I like the fact that everything is integrated and the documentation seems to be extremely well planned. I can remember that there was another shop module for PW around that looked promising but offered little to no documentation at all. What a bummer.

Thanks @maximus the title format is working now! I was somehow expecting to see that the {site_name} (or whatever suffix you enter here) will be added and visible in the bulk editor window: Currently only the page title value is visible. However when viewing the page in the frontend the title format from the module settings is shown correctly. So I can confirm that this works now.

Thanks @maximus I installed the new version but I can't seem to make it work. For "Rendering" I am using this values {meta_title} | {site_name} The "site_name" is added when viewing the page in the frontend but the "meta_title" (resolved from field:title in the global defaults JSON) is missing. I rebuild the index multipel times but cannot see the title (or description) here either: I have placed some default values for title and description in my config next to the new "title format" options and would assume that those values should be visible after making an audit:

I have to type in quite a few numbers a day, its just more convenient for me.

Nice view you got there. But I could never ever work on a keyboard without a numeric keypad 😉

Yeah I just installed this module too and when comparing your module with that from maximus (and the old trusty Seo Maestro) there is no perfect "all in one" solution. Each module does something better than the other and vice versa! I think it is still mandatory to try out what module fits for your projects and fills out the gaps in your personal workflow. For example: I like that @maximus module includes sitemap generation and redirect handling I like that your module offers per-template defaults and so on...

Sounds great. I will give this module also a try 🙂

Hi @maximus I am using SEOMestro at the moment but saw that this module has a convenient migration feature for that case. Really nice! Is it possible to automatically add a "suffix" to the meta_title? What I like to to is created titles like: "Home | my-company.com" or "Our Services | my-company.com" Where the first part is the actual page title and the second part is my suffix text. Is it somehow possible to define this pattern in the global configuration of the module inside this global defaults JSON? { "meta_title": "field:title", "meta_description": "field:summary|truncate:160" }

For all who are interested in this module: I have been a tester in the past and this module is excellent. I am using it now in every project at it makes asset handling (not only images but think of pdf, mp3, video, etc.) a breeze. This module acts as a missing link for global media management in ProcessWire.

Hi @Mikel I use a custom JavaScript function (that name is entered in the PrivacyWire module settings) to check for consent and then set the cookie for activating NativeAnalytics: function initNativeAnalytics() { const consent = JSON.parse(localStorage.getItem('privacywire')); //console.log(consent); if (consent && (consent.cookieGroups.statistics || consent.cookieGroups.marketing)) { document.cookie = "pwna_consent=1; path=/; max-age=" + (60*60*24*365) + "; SameSite=Lax"; if (window.PWNA && typeof window.PWNA.trackIfConsented === 'function') { window.PWNA.trackIfConsented(); } } else { document.cookie = "pwna_consent=; path=/; expires=Thu, 01 Jan 1970 00:00:00 GMT"; } }