Jump to content

Recommended Posts

Just now, Lutz said:

Media Manager for storing the images?

Each media is a PW page, hidden in admin part of the tree. Non-supersusers never get to see them :-).

Share this post


Link to post
Share on other sites
27 minutes ago, David Karich said:

Apropos: I never received a download link for the update to 012 by mail. Or do I have to buy a new license?

Subscriptions (update + VIP support) are valid for 1 year. After that you can renew for a fraction of the original price. Otherwise, I don't send out update reminders but post here in the forums. If you have a valid subscription, you can use the resend download links form to get an email with the download link to the latest version (or use the link in the original email you received after purchase). For renewals, please use the renewal form. Any problems, please PM or send me an email.

  • Like 1

Share this post


Link to post
Share on other sites
47 minutes ago, kongondo said:

Each media is a PW page, hidden in admin part of the tree. Non-supersusers never get to see them :-).

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Share this post


Link to post
Share on other sites
33 minutes ago, Lutz said:

@kongondo To prevent a misunderstanding: each media is stored in the database, not in the file system?

Sorry I wasn't clear.

Media = $page

Media has one MM field. In the case of images, it is an multi image field. So $page->image_field will give you the image

Media has a title field: $page->title;// title of your media

If you had own fields to Media, you can access them using $page->your_field, as usual.

However, we don't use the variable $page. Instead what you get is a MediaManager Object.

So, Media page object is $mm.

Echo $mm->id: id of the media

Echo $mm->title;

// this is the image field

foreach($mm->media) {

}

Hope this makes sense.

 

Share this post


Link to post
Share on other sites
31 minutes ago, kongondo said:

Hope this makes sense.

 

@kongondo Yes, thank you, this is what I had expected and hoped for. My question was in terms of scalability, regarding file system limits. In PW, files are stored in subdirectories under /site/assets/files, therefore we normally have to deal with max directory limits (e.g. 32k). We have $config->pagefileExtendedPaths, but it's marked as beta. So as you mentioned +500k, I hoped for an info regarding the stability of pagefileExtendedPaths (or another way to avoid collisions with max directory limits). When they manage +500k, did they enable pagefileExtendedPaths?

Share this post


Link to post
Share on other sites
1 hour ago, Lutz said:

When they manage +500k, did they enable pagefileExtendedPaths?

I have no idea. I never asked. I could try and find out.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for this awesome module! Here is some feedback after some hours of testing: When using MediaManager along with Ryan’s ProDrafts, I had to manually disable ProDrafts support for the MediaManager specific templates. Otherwise, inserted images from the MediaManager would not display in the saved pages (neither drafts nor published versions). I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

  • Like 1

Share this post


Link to post
Share on other sites
11 hours ago, tb76 said:

Thanks for this awesome module!

Glad you like it.

11 hours ago, tb76 said:

I figure this was because the images in MediaManager were by default also handled as drafts. After disabling ProDrafts for the MediaManager templates, everything – including working with drafts – works just fine.

Thanks for testing and reporting back. I guess it doesn't make much sense to have a draft media (i.e. using ProDrafts). However, if you have added other fields to your Media Manager templates, you might want those to work with drafts. Hmm. I've never used ProDrafts before but you've given me something to think about.

Share this post


Link to post
Share on other sites

Hi kongondo,

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Greetings,

Thomas.

  • Like 1

Share this post


Link to post
Share on other sites
On 6/21/2019 at 3:57 PM, xportde said:

one of our customers asks, if it would be possible to write out not only the usage amount of media manager items, but also all usages as list with concrete info about field, page etc. I know, this isn't going to be easy, but maybe it's worth the effort, if other users reported the same idea?

Hi Thomas,

I'll have a think. The interface will need careful thought as it would need to be separate from the tooltip.

Share this post


Link to post
Share on other sites
On 5/10/2019 at 3:09 PM, kongondo said:

However, two people have reported an error about class ProcessMediaManager not found in line 20 of MediaManagerUtilities.

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Share this post


Link to post
Share on other sites
On 7/31/2019 at 6:23 AM, elabx said:

Three people now! haha

Any news on this bug?? Thanks!

I rolled back but now I am having issues with JqueryUpload version 008 working, tried rolling back to 002 but I still can't open when I click on Add Media on any of the pages, getting:

 Uncaught Error: Class 'ProcessWire\JqueryFileUpload' not found in /srv/users/serverpilot/apps/ladosis/public/site/modules/ProcessMediaManager/ProcessMediaManager.module:209

Ok this took me through a tour of namespacing issuer all over the MediaManager modules and got it working back. 

Hey @elabx,

Sorry for the delay in responding. I have just tested in a new PW install with only 3 modules: MM, JFU and Tracy. I had to click on Clear Compiled Files 3 or 4 times for it to finally work. Here's what I did.

  1. Upgrade JqueryFileUpload by overwriting the existing files
  2. Delete MediaManagerTabs.php and pocketgrid.css in the current (old) Media Manager install
  3. Overwrite MM version 011 files with version 012 files
  4. Access Media Manager
  5. You might see Class not found error (either MediaManagerUtilities or JqueryFileUpload
  6. Access Modules (on same tab in #4) and click on Clear Compiled Files
  7. Once step #6 is finished, click browser back button to go back to Media Manager.
  8. If you get class error again, repeat steps 6 - 7 as necessary

Please let me know if this works for you. Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo Finally managed to updated!! But you know what, now I didn't have to clear anything, it just worked after a module refresh!! Just so you have more info, the only difference was that I namespaced the old modules (in a desperate attempt to bring back everything to work because it kind of broke after I rolled back from my first install failure). honestly don't have very clear what happened, but indeed the new version works flawlessly.

Questions/issues: 

  • I don't seem to be able to drag and drop over the Inputfield. I can give you access to my site if you need to debug.
  • I cannot seem to find the edit button for the image description now, the one that was placed at the top right? Is there a new way to edit the descriptions? Appending how my images look when I click on them.   Jut realized now this is done in a normal, maybe you could enable an Edit link right on the Inputfield? At least on my site it's not showing, I'd guess that's the most practical for editors, instead of opening the Media Manager Popup.
  • I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

All my questions crossed where solved configuring the Inputfield :)

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Share this post


Link to post
Share on other sites
10 hours ago, elabx said:

Just so you have more info, the only difference was that I namespaced the old modules

Aah, nice workaround. I never thought to do that 😊.

10 hours ago, elabx said:

This is a GREAT update kongondo! I know this has been mentioned before but the improvement in the UI is a huge plus! I see you mentioned you have a lot of users that had never mentioned this, but in my case as with other PW users, all my clients complained about the lack of polish in UI, but this update really solves a lot of the inconveniences. 

Glad you like it :-).

10 hours ago, elabx said:

I cannot get the alt text on images placed in CKEditor to update accordingly, I also have the setting updated in the Inputfield configuration, have you had any issues with this?

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

Full documentation is available here, by the way :-).

Thanks.

Edited by kongondo

Share this post


Link to post
Share on other sites
5 hours ago, kongondo said:

I don't follow. What is this alt text please? Please clarify which inputfield configuration, CKEditor or MM?

 

When you insert an image through CKEditor, ideally I'd want to grab the description from the image's description field. CKEditor Inputfields fields have an option called "Image management" that should enable this:

https://processwire.com/docs/fields/textarea-fieldtype/#markup-html-option

I just can't get this to work well, if I add a new image to the text fields, their descriptions are not pulled from the images. 

My bad again man, I kept on reviewing this on the CKeditor source and just realized this is done on runtime. 

Share this post


Link to post
Share on other sites
21 minutes ago, elabx said:

My bad again man, I kept on reviewing this on the CKeditor source and just realized this is done on runtime. 

😀

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo Thank you for that module. Befor I go and order it, I'd like to make sure that the feature my client needs is included already.

For that client each media item should be available as a public download. So in the list of media in the manager there should be something like a button to copy that public link and when editing media that public link should be displayed also.

I guess the module needs some customizing to do this. Would this be possible through hooks? Especially for the media lists in the manager. Are there hooks available where I could inject some markup or even an extra column in list view?

Since all media are pages, I guess I can hook into ProcessPageEdit for those templates and add the link to display in the page editor screen? 

Share this post


Link to post
Share on other sites
On 8/28/2019 at 10:54 AM, gebeer said:

So in the list of media in the manager there should be something like a button to copy that public link and when editing media that public link should be displayed also.

Where is the link being copied from?

On 8/28/2019 at 10:54 AM, gebeer said:

Since all media are pages, I guess I can hook into ProcessPageEdit for those templates and add the link to display in the page editor screen? 

Yes, but Media Manager methods are currently not hookable. I'm not sure you've seen it, but Media Manager allows you to add your own (ProcessWire) fields to the media pages templates. Those will then be displayed in the list (table) view if you configure them to be displayed in Media Manager settings. However, you will not be able to edit the values directly in the table view. Instead, each media has an edit link that when clicked will open the full page for editing - this is a normal (almost) ProcessWire page edit form. You can use it to edit any of the fields in the template as well as the media themselves. In the frontend you access them as $m->your_public_link_field. I hope this makes sense. If not, please let me know.

Thanks.

Share this post


Link to post
Share on other sites

Hi kongondo!

Recently, I used Media Manager in a client project. In this real world use case, the media library very quickly grew to an extent, where it was too confusing for the client. Of course I know how to apply filters, but for my client, configuring and applying filters was to complicated - even with the relatively new feature of pre-defined filters. So I thought I would ask you, if you could image to implement some additional filter-features, that would make it easier for clients:

- It would be great, if it was possible to set a default filter for every MediaManager-Field. I have a lot of different "image-types", like icons, fotos, sketches and so on. With such a feature, it would be possible to limit the displayed images to just the "type" of image, that suits the context of the current MediaManager-field. Like when applying some product icons, you don't want to choose from the whole library with all the staff portraits.

- Another great feature would be, if pre-defined filters could be applied with one click in the overview. I tried to sketch this in a fake screenshot:

image.png.e2ba4df88805529eb8e8537ea84bd795.png

In this way, an admin could pre-define all needed filters, and the user/client could just apply them with one click - without worrying about or even understanding the actual filter definition.

I guess those features don't exist already, but if so, I would be very happy, if you could point me to any existing solution.
Otherwise it would be great to have those - or similar - features in a future version.

Thanks again for the great module!

Share this post


Link to post
Share on other sites
On 11/29/2019 at 1:33 PM, nurkka said:

Recently, I used Media Manager in a client project. In this real world use case, the media library very quickly grew to an extent, where it was too confusing for the client.

Hi @nurkka. Sorry for the late response. I have been away.

On 11/29/2019 at 1:33 PM, nurkka said:

It would be great, if it was possible to set a default filter for every MediaManager-Field. I have a lot of different "image-types", like icons, fotos, sketches and so on. With such a feature, it would be possible to limit the displayed images to just the "type" of image, that suits the context of the current MediaManager-field. Like when applying some product icons, you don't want to choose from the whole library with all the staff portraits.

This is an excellent suggestion! I'll have a think on how to best implement it but theoretically, it is doable.

On 11/29/2019 at 1:33 PM, nurkka said:

In this way, an admin could pre-define all needed filters, and the user/client could just apply them with one click - without worrying about or even understanding the actual filter definition

Another great suggestion! I would have to rethink the GUI a bit since tabs (Filter: Icons, Filter:Photos, etc) would quickly become unwieldy. 

On a related note, I have been planning to refactor the items shown in the Inputfield Selector (the filters) as there are a number of things not directly relevant to Media Manager that would confuse editors. For instance, the Inputfield shows non-Media Manager fields, items like Path/URL, etc.

I am planning to work on your suggestions and the refactoring in the next update.

I might call on you for a bit of testing before release, if that's OK.

Thanks. 

  • Like 2

Share this post


Link to post
Share on other sites
On 12/8/2019 at 2:04 PM, kongondo said:

I might call on you for a bit of testing before release, if that's OK.

Hi @kongondo, thank you for your feedback. I am glad that you like my suggestions. And I would be happy to help you with testing!

  • Like 1

Share this post


Link to post
Share on other sites
On 12/15/2019 at 6:28 PM, nurkka said:

And I would be happy to help you with testing!

Thanks!

Share this post


Link to post
Share on other sites

Hi kongondo,

because there's no option for limiting uploaded images to image width and/or height in MM settings (or is there?), we've found out, that the PW-native image field limitations from the underlaying field media_manager_image works (input > maximum image dimensions). Unfortunately, this restriction works quiet, i.e. the MM-upload will be finished without error or warning, but the image will correctly not stored because of violating the image field dimension rules.

Would it be possible to apply the image field rules already in MM upload screen, so that the user can see possible violations before start uploading (like the maximum file size rule from MM settings)?

Greetings,

Thomas.

Share this post


Link to post
Share on other sites
1 hour ago, xportde said:

there's no option for limiting uploaded images to image width and/or height in MM settings (or is there?),

Actually, there is 😁. See under Settings > Upload Settings > Image. There are settings for min/max height and min/max width. These are directly coupled to the the field's (media_manager_image) corresponding settings. If you change one it will change the other. However, I have just noticed a bug. The min values are decoupled! This shouldn't matter much though since Media Manager will still honour the min values. I will fix these later (i.e. the 'decoupling' issue).

1 hour ago, xportde said:

so that the user can see possible violations before start uploading (like the maximum file size rule from MM settings)?

Excellent suggestion! I will add this to my TODO as well. 

NO ETA for above, just yet, sorry. I hope it isn't urgent?

Thanks!

 

 

 

Share this post


Link to post
Share on other sites
Quote

Actually, there is 😁. See under Settings > Upload Settings > Image. There are settings for min/max height and min/max width

Do you mean Image maximum width / height? So I misunderstood the notes Maximum width / height of resized images (pixels), I thought, this settings are for resizing, not for uploading? But in fact, it corresponds with the equivalent image fields. Maybe you could write the notes accordingly (Max width / height for uploaded images)?

Greetings, Thomas.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...