Jump to content

Media Manager


kongondo

Recommended Posts

Do you mean in the Inputfield (what you see when editing a ProcessWire page with a Media Manager field) or in the Media Library itself? I ask because there are no tabs in the former. The settings for fields only affect individual fields and are not universally applied to the Media Library (the manager itself). But there was a bug in the former in the text being displayed in the Inputfield and I fixed that in MM version 002.

I grappled with this (the first part of your statement) during development and settled for highlighting the title with a view to revisiting in the future. Will have a look again. As for the Edit and Crop buttons, I don't understand what you mean. Please clarify.

Am not sure I follow. Are you talking about the Media Library or a Media Manager field - Inputfield?

Media Manager displays a notice (success or failure notices) when you select media and click on 'Insert Media'. Are you not seeing this in your tests? As for closing the modal window, the idea is that one may want to insert more media from other Media Library pages not currently in view. Closing the window would mean they have to open the modal again in order to insert the other media. I have explained this in the (upcoming) documentation so as not to confuse users.

Hi Kongondo, apologies for delayed reply...

Fore reference I have MM v0.0.2 and PW dev 3.0.12.

1. Re inputfield - yes I've created a new field and applied to page (only ticked Image when creating the field).  When I then go to edit a page with this field, it says "Allowed Media Types: Image".  If i click Add Media in that field the modal pops up and I see tabs at the top for All, Audio, Document, Image, Video, Upload.  The field type is "Media Manager" - have I used the wrong field type?

2. Yes I don't know the answer for the highlighting - it's probably just something you get used to.  Same with the Edit and Crop buttons - on a dark image you just can't see them unless you hover on the large image on the right hand side.  Again, probably just something that can be trained into users, I'm being picky :-).

3. My ideal workflow for users when editing a page is, open media library from the page field to select an image to insert.  There would be only the images displayed (no All, Audio, Document etc).  To upload a file from that window they could just drag n drop a file to that modal window and it would get added to the image list.  This might be a moot point if I've set up wrong re point 1 above.

4. Yeah I'm seeing the success notifications.  I just can't think of a time when a user would need to do more than one action in that modal window.  If they want to insert multiple images they'd just highlight them all then click Insert (which is what happens now).  If they've done that then they don't need the modal window open any more.  I admit this may not be the workflow for everyone but in the instances I can think of for my users, 95% of the time having the window close on successful insert would be preferable.  I take your point about having multiple pages to scroll through changing this.  I suppose the vast majority of my use cases are inserting only one image per field (ie it's an image field rather than a carousel).  Maybe there could be an "Insert & Close" button in addition to the "Insert Media" button?  Depends whether you think that makes it more cluttered/confusing vs benefit.

Link to comment
Share on other sites

@Loges

#1: I now get it. When you click the link 'Add Media' the modal it opens is essentially the Media Library part of Media Manager, i.e. ProcessMediaManager, but styled slightly differently from what you see when you directly access the Media Library from the ProcessWire admin menu. I am working on a way to only show navigation/tab items that are relevant to the current field you are inserting to. So, in your case, if you only had images, the only tabs you should see are 'Images' and 'Upload'. If you had allowed, say documents and video, then, you would only see 'Documents Video Upload'. You need a media tab since you would need a way to navigate back to your Media Library  if you went to 'Upload' tab.

#2. Highlighting of the active media (i.e. the media being previewed) has been sorted in MM v003. Did you get my email notification? As for highlighting the crop, edit, icons, that should be sorted with some minimal training. They will always be on the right hand side. :-)

#3 Sort of covered in #1?

#4 I'll look into insert and close

Link to comment
Share on other sites

  • 3 months later...

Media Manager version 004  (released (01/08/2016))

Happy to announce the latest release of Media Manager.

Changelog

  1. FieldtypeMediaManager/InputfieldMediaManager: Configurable setting to insert media in inputfield and close modal. Set in the Details tab of your FieldtypeMediaManager field
  2. Fixed bug where non-allowed media types (for those limiting media types available to InputfieldMediaManager) would still show up in the results in the selection modal. 
  3. Fixed bug where the menu item 'All' would not appear in the InptufieldMediaManager media selection modal even if  allowed media types was limited to at least 2 types
  4. By popular demand, a CKEditor image plugin! mmimage (cloned and adapted from pwimage :) thanks @ryan) lets you insert images in your Media Manager Image Library directly into the rich text editor. See a video demo + instructions here

 

@TODO:

  • Multi-tagging of media
  • Documentation (thanks for being patient with me guys...)

 

  • Like 5
Link to comment
Share on other sites

On 03/08/2016 at 2:59 AM, Tyssen said:

Does MediaManager work in repeating fields and if not, is that on the roadmap?

Until your question, it wasn't :)....I have made some minor changes to version 005 which now enables this. I'll try and commit this today, if not, then over the weekend. 

Thanks for your interest in Media Manager...

  • Like 3
Link to comment
Share on other sites

I haven't tried it yet, but this module looks great!

I'm guessing the Media files are stored using PW pages?  Is there any way to add more fields to those PW pages?  For example, I might want to use a text field to store where I got the image from.

I'm also curious how the File Usage works?

  1. Does it just count and list the pages where the media file is used in a media field.
  2. Does it also take into consideration files that have been inserted into text areas?
  3. Does it include pages with text areas that link to the files?
Link to comment
Share on other sites

Media Manager version 005  (released (07/08/2016))

Happy to announce the latest release of Media Manager.

Changelog

  1. Media Manager in Repeaters: Media Manager (Fieldtype- and InputfieldMediaManager) can now be used in Repeaters with full access to your Media Library.  Demo video and instructions are here.
  • Like 1
Link to comment
Share on other sites

On 05/08/2016 at 10:00 PM, gmclelland said:

I'm guessing the Media files are stored using PW pages?  Is there any way to add more fields to those PW pages?  For example, I might want to use a text field to store where I got the image from.

I'm also curious how the File Usage works?

  1. Does it just count and list the pages where the media file is used in a media field.
  2. Does it also take into consideration files that have been inserted into text areas?
  3. Does it include pages with text areas that link to the files?

 

Storage:

Stored in page: Yes. Please see the OP, about half-way down

Custom fields: Yes if you add them directly to the templates but you will not be able to edit those custom fields using the MM interface. In addition, MM pages are hidden in the admin so editing your custom fields will not be ideal (or accessible to normal users). Alternatively, you can use images/files native description and tag fields. These are currently editable directly in your Media Library.

File Usage:

  1. It counts the actual usage in FieldtyeMediaManager field in the DB
  2. No
  3. No
Link to comment
Share on other sites

  • 2 weeks later...
2 hours ago, Jonathan Claeys said:

I'm having a big issue with the module. When I added an image to my page and I try to get the URL of it, it just returns "null". I've been searching, trying for hours now. 

What ProcessWire version are you using with this module and it would greatly help if you would go into more detail about your problem?

Link to comment
Share on other sites

1 hour ago, cstevensjr said:

What ProcessWire version are you using with this module and it would greatly help if you would go into more detail about your problem?

I'm using version 2.8 of Processwire and I added media to my page. Wich works fine. I do a var_dump of my media and I get back an object with 1 image, wich is also correct. The problem is that the object doesn't include a url. Normally you do: $image->url or $image->size(x, y)->url but this doesn't work on the media I added by the module. And when I just look to the examples on the media manager documentation it should work like that. Or am I overlooking something?

Link to comment
Share on other sites

@Jonathan Claeys Please provide an example of the code you are using to try and get your media image URL.

I haven't used Media Manager, but looking at the documentation for outputting to the front-end there are a couple of things to be aware of:

1. A Media Manager field returns an array (specifically a 'MediaManagerArray') so you need to treat it as such in your template even if it contains only a single media item. The docs suggest looping over it, but if a MediaManagerArray is also a WireArray (the docs aren't specific about that) then you could use other API methods to get items such as first() or get($key).

2. The media itself (an image in your case) is contained in the media property of an individual MediaManager object. So you need to use methods like url or size() on the media property and not on the MediaManager object.

Assuming that a MediaManagerArray is a WireArray and that your Media Manager field is called my_media_field:

$media_manager_array = $page->my_media_field;
$media_manager_object = $media_manager_array->first();
$image_object = $media_manager_object->media;
$url = $image_object->url;
echo "<img src='$url'>";

This is just to give you the idea, and is more verbose than necessary.

  • Like 3
Link to comment
Share on other sites

8 hours ago, Robin S said:

@Jonathan Claeys Please provide an example of the code you are using to try and get your media image URL.

I haven't used Media Manager, but looking at the documentation for outputting to the front-end there are a couple of things to be aware of:

1. A Media Manager field returns an array (specifically a 'MediaManagerArray') so you need to treat it as such in your template even if it contains only a single media item. The docs suggest looping over it, but if a MediaManagerArray is also a WireArray (the docs aren't specific about that) then you could use other API methods to get items such as first() or get($key).

2. The media itself (an image in your case) is contained in the media property of an individual MediaManager object. So you need to use methods like url or size() on the media property and not on the MediaManager object.

Assuming that a MediaManagerArray is a WireArray and that your Media Manager field is called my_media_field:


$media_manager_array = $page->my_media_field;
$media_manager_object = $media_manager_array->first();
$image_object = $media_manager_object->media;
$url = $image_object->url;
echo "<img src='$url'>";

This is just to give you the idea, and is more verbose than necessary.

Thanks alot,

I just saw my problem. I didn't see you had to call the method ->media also after you got your image field already. :) That solved the problem. 

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

I am now back and slowly catching up with issues. Thanks for your patience.

 

Thanks @Robin S for helping out above. @Jonathan Claeys, many thanks for using Media Manager. Please let me know if you need further clarification.

I can confirm that a MediaManagerArray is a WireArray. I have updated the docs to reflect this.

Link to comment
Share on other sites

  • 2 weeks later...

Media Manager version 006  (released 21/09/2016)

Happy to announce the latest release of Media Manager.

Changelog

  1. mmlink: A CKEditor link plugin (cloned and adapted from pwlink :) thanks @ryan) lets you insert links to the media in your Media Manager Library directly into the Rich Text Editor (RTE). (Instructions on how to setup are similar to those of mmimage as shown in this video. Where it says MMImage/mmimage please replace with MMLink/mmlink respectively, thanks). The plugin is in the folder MediaManager/plugins/mmlink. Please note that currently it is not possible to edit a link's attributes (e.g. rel, target and title). However, a title is auto-inserted in the link (the respective media's title.

Please download latest release of the module from the link in your purchase confirmation email. Let me know if you encounter any issues, thanks.

@TODO:

  • Multi-tagging of media
  • Documentation (thanks for being patient with me guys...)
  • Like 2
Link to comment
Share on other sites

I have just purchased and installed Media Manager and I have an immediate couple of questions which will determine whether it's actually useful enough for my requirements:

What is the purpose of the image tags? Will it be (or is it already) possible to filter images by a specific tag?

 

I would like to be able to add a whole bunch of images and tag them as 'icons', so that I can filter by that specific tag to see those images only.

If this is not possible, perhaps there's a way to achieve the same result which I'm missing. Please could you help? Thanks.

Link to comment
Share on other sites

Hi @spacemonkey95. Thanks for the purchase.

Media Tags: The purpose of 'media tags'...is the same purpose as in ProcessWire (please note: all media can be tagged; not just images); namely, to group related media (images, documents, video or audio) to fulfil any number of functions - easier organisation, finding related things, etc. 

Filtering media by tags: Yes, it is already possible to filter images (or any other media) by tags both in the API and in your Media Manager Library (the Process Module). Please see the gif below.

What is pending is the ability to tag multiple media in one go. Currently, one can only tag one media at a time as shown in my post above. This can be tedious, hence the need for multi-tagging capability. I have started work on this new feature but it won't be ready this week but soon. It is also not possible, currently, to sort media by tags (i.e. the display of media in the Media Library - currently sorted by title). I am also working on implementing this.

Hope I've answered your questions.

Filtering media by tags

media-manager-media-tags-filter.gif

Edited by kongondo
clarity...
  • Like 1
Link to comment
Share on other sites

Hi @kongondo

Our Agency has purchased your Media Manager which is great Module. But I encountered a few Bugs/Problems. 

On localhost (ProDraft, Multilanguage Fields respectively the multilange installation profie of processwire):

1. Can't upload Videos

video fehler.png

2. Cant change or edit Tags field (it always stays empty no matter what i do).

3. The variations problems is also active here

General Problems on Server (Uses Different Hooks, ProDraft, Multilanguage Fields etc...):

1. Cant change or edit Description field (sometimes it works once).

2. Cant change or edit Tags field (it always stays empty no matter what i do).

3. Variations functionality(cropping, changing dimensions etc...) doesnt work (It just makes a exact copy with the same dimensions and adds it to the file/image field of the  page)

When I upload the image

variations3.png

 

When I use the variations functionality

variations2.png

variations.png

 

Don't know if this is usefull for debugging (All Hooks):

	$this->addHookBefore('ProcessHome::execute', $this, 'rootPage');
	$this->addHookAfter("Page::editable", $this, 'setEditAccess');
	$this->addHookAfter("Page::addable", $this, 'setAddAccess');
	$this->addHookAfter("ProcessPageLister::getSelector", $this, 'setListerAccess');
	$this->addHookAfter('ProcessPageList::execute', $this, 'hidePages');
	$this->addHookBefore('ProcessPageAdd::executeTemplate', $this, 'redirectParent');
	$this->addHookAfter('ProcessPageListRender::getPageLabel', $this, 'addTemplateLabel');
	$this->addHookAfter('ProcessPageAdd::buildForm', $this, 'addFields');
	$this->addHookAfter('ProcessPageAdd::buildForm', $this, 'collapseName');
	$this->addHookAfter('ProcessPageEdit::buildForm', $this, 'addLangViewTabs');
	$this->addHookAfter('ProcessPageEdit::getTabs', $this, 'removeDefaultViewTab');
	$this->addHookAfter('InputfieldForm::render', $this, 'renderForm');
	$this->addHookAfter('ProcessPageAdd::execute', $this, 'addScript');
    $this->addHookBefore('WireMail::send', $this, 'fixOutlookMail');
    $this->addHookAfter('Pages::save', $this, 'hookSave');
    $this->addHookAfter('Pages::clone', $this, 'hookClone');

When I deactivate all Hooks the Problems are still there.

 

PS: I deactivated the draft functionality for the media manager templates.

Link to comment
Share on other sites

Saving Variatons in different Dimension works... I didn't recoginzed the radios.... My bad :D But when I save a variation with the same dimensions it still looses the original.

PS: But the cropping functionaliy also doesn't work. It just copy the original one and looses the original afterwards.

Link to comment
Share on other sites

Hi @Nukro,

Thanks for the purchase. Apologies for the 'rough start' :-)

1. Uploading Videos:

  • Have you specified .mp4 as an allowed extension? If not, you need to do that under Upload, then Settings Tab, scroll down to Settings: Video > Valid video file extensions
  • What error is returned in the console (in response to the ajax request)?
  • It could be an allowed file size issue. The error returned by the server will shed light on this

2. Editing Tags:

  • Did you enable tags for the 4 media templates? Please have a look at the install instructions here, thanks. I have tried and have so far been unable to programmatically enable tags on install

3. Variations

  • Hmm, that's quite a number of issues. 
  • Cropping: are you using Save as Copy?
  • Are you developing locally or could I get some temporary access to the site to have a look around?

PW version? Currently we don't officially support version 3 until there is an official release (which is soon!)

Edit:

How are you uploading images/media? In your screenshot above I see you are directly editing an image...

 

Edited by kongondo
additional info
  • Like 1
Link to comment
Share on other sites

21 minutes ago, kongondo said:

Hi @Nukro,

Thanks for the purchase. Apologies for the 'rough start' :-)

1. Uploading Videos:

  • Have you specified .mp4 as an allowed extension? If not, you need to do that under Upload, then Settings Tab, scroll down to Settings: Video > Valid video file extensions
  • What error is returned in the console (in response to the ajax request)?
  • It could be an allowed file size issue. The error returned by the server will shed light on this

2. Editing Tags:

  • Did you enable tags for the 4 media templates? Please have a look at the install instructions here, thanks. I have tried and have so far been unable to programmatically enable tags on install

3. Variations

  • Hmm, that's quite a number of issues. 
  • Cropping: are you using Save as Copy?
  • Are you developing locally or could I get some temporary access to the site to have a look around?

PW version? Currently we don't officially support version 3 until there is an official release (which is soon!)

Edit:

How are you uploading images/media? In your screenshot above I see you are directly editing an image...

 

Thanks for you quick Answer @kongondo

I'm testing the media manager at the moment on localhost with a blank processwire install

1. Uploading Videos:

.mp4 is specified as an allowed extension. I looked into the console and I am getting this error from the ajax call:

variations.png

2. Editing Tags

Thanks. I enabled now the tags for the media manager fields. It works now.

 

3. Variations

For cropping I am using 'save as copy'. It just makes a exact copy of the origin image and afterwards it looses the original one. The same happens when I save(save as copy) the image with the original dimensions.

 

4. Uploading Images/Videos

I'am uploading all the files from the upload tab in the media manager module (jqueryfileupload).

Link to comment
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • 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.

      Detailed records
      View mode "Detailed records" 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.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      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 (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      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.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...