Jump to content

Media Manager


kongondo

Recommended Posts

On 10/29/2020 at 2:29 PM, RyanJ said:

I am unable to successfully return images with the getTag() or findTag() methods that are available. Am I misunderstanding something? 

Media Manager Field. Returns empty string

A Media Manager field is not the same as an images field. It has no getTag() or findTag() methods. Please read more about this here and here. Currently, there is no direct way of achieving what you want.

  • Thanks 1
Link to comment
Share on other sites

  • 5 weeks later...
On 12/1/2020 at 5:50 PM, toni said:

@kongondo 

I’ve just bought media manager and installed it on a fresh pw instance.
 
 
Unfortunately an upload does not appear (small logo image)
and no error is thrown.
 
The User is a super user. Any idea what could go wrong?
Thanks,
 
 
Toni

Hi @kongondo

I do have the same probleme like @toni, what he showed in his video. My settings: newest mysql and php versions, PW 3.0.165 and Media Manager (Process) v0.1.2 β

The following didn't change anything:

On 6/4/2020 at 6:08 PM, kongondo said:

By the way, a quick workaround, if you insist on living on the edge is to do the following:

  1. Edit a Media Manager field (e.g. media_manager_image)
  2. Change its Use Tags setting and save
  3. Revert the change to what it was before and save again

Uploads should now work.

Note though that using the 'Cleanup' feature might still throw the PDO error linked to in the post above.

Thanks for your help

Link to comment
Share on other sites

Hi @panx,

Apologies for the issue you are facing. 

@toni's issue was resolved by following steps similar to what you tried above. It was caused by the ProcessWire tags issue discussed here and reported here. I have now set up a troubleshooting guide (WIP) in the documentation to help with this. Please try that first and let me know if your issue is still unresolved. 

Thanks.

  • Like 1
Link to comment
Share on other sites

26 minutes ago, dynweb said:

I would like to download the new version from my download link, but it seems to be the same version that I bought in May 2020. It always says v0.1.2

 

39 minutes ago, kongondo said:

It still says version 12 but grab it from your download link and install that version. It resolves the issue.

😉. Please see my post above yours.

 

19 minutes ago, entschleunigung said:

The Download link from your email results in a 404?!

If your purchase date is more than 12 months, then the link has expired. Please confirm that and let me know. I can send you the relevant file to update via email. For anything involving order numbers etc, please either send me an email or a PM.

Thanks.

  • Like 1
Link to comment
Share on other sites

  • 1 month later...

I am getting the following error when i add the InputFieldMediaManager to a template and edit a page of that template. 

`call to member funnction countr() on null`

on line `$this->mediaManagerField->currentFieldCnt = $currentPage->$mediaManagerField->count();`

Image:
https://gyazo.com/b428b27b498789e7a5d7d91958979c3b

- I've reinstalled Media Manager.
- I've updated to the latest ProcessWire. (3.0.170)

Link to comment
Share on other sites

Hi @StanLindsey,

I haven't seen that one before :-). Could you please tell me more about what's on that template? Assuming you have TD installed, could you please tell me/show me the output of the following?

Please add the following debug calls:

<?php
// around line #369 in the method ___render() in InputfieldMediaManager.module
bd($this->mediaManagerField, 'MEDIA MANAGER FIELD');

// around line #38 in the method __construct() in MediaManagerRender.php
bd($mediaManagerField,'MEDIA MANAGER FIELD');

edit: What's the name of your Media Manager Field?  Is it all lower_case?

Thanks.

Edited by kongondo
Link to comment
Share on other sites

Hi Kongondo,

Hope your well. 

After looking through this thread, I am not seeing anything specific to my question. So I am dropping it here.

To better explain what I am trying to do, I will give a brief structure of my site. I have a directory which contains multiple locations as parent pages. Each location can have multiple child pages. Location and child pages contain a media manager field which currently pulls in all images allowing the user to select from those. 

What I am looking for is restricting images based off the location page and or child pages of that location that is being edited.

Example: I am editing Location A or any child page of Location A and when I click "Add media", the run time hook would restrict/filter the list of available images that have been tagged as Location A. If a tag wont work, maybe a custom field.

Is there some sort of hook to achieve this functionally?

Thanks for your time. 

Link to comment
Share on other sites

Hi @RyanJ,

42 minutes ago, RyanJ said:

Hi Kongondo,

If you want to tag a forum member, please use the @ symbol followed by their handle 😄. I just stumbled on this post...otherwise, might have missed it.

43 minutes ago, RyanJ said:

After looking through this thread,

Did you mean to post in some specific thread? Looks like you've started a new topic instead 😀.

44 minutes ago, RyanJ said:

Is there some sort of hook to achieve this functionally?

Please point me to or move your question to the original thread you were trying to reference. I have no context about your question so cannot provide any useful response.

Link to comment
Share on other sites

Hi @RyanJ,

We are home now...moved us here 😄.

2 hours ago, RyanJ said:

Is there some sort of hook to achieve this functionally?

Currently no...but..

2 hours ago, RyanJ said:

Example: I am editing Location A or any child page of Location A and when I click "Add media", the run time hook would restrict/filter the list of available images that have been tagged as Location A. If a tag wont work, maybe a custom field.

If it is simply an issue of giving editors the convenience of easily selecting the images that can be added to the page being edited, we could probably get away with a URL string appended to the URL that opens the modal which Media Manager would be able to read from when the page opens. Alternatively, we could get away with URL segments, which we already have for the page opening the modal and read the settings for that Media Manager field (e.g. with tags, etc) that should be used for filtering the media for the page being edited. However, if the usage is for something more restrictive, e.g. control access to media depending on some user permissions, then that would require some additional checks. I am just thinking out loud here (note-to-self-sort-of).. :-).

Let me have a think, please.

Thanks. 

Link to comment
Share on other sites

Hi @kongondo

Thanks for getting me in the correct thread. I am not sure how I managed to get lost. 

I think role based would be useful, but I url segments would work for sure. The restriction would be based off the "Parent Page", so Location A and any child pages of Location A being edited, would only get Location A images. 

Maybe disabling filtering could be an option to not allow the client to filter on different images other then what is in the url segment. 

The same concept would need to occur if they added a new image as well. It would automatically get tagged or whatever is used for filtering the images. So and uploaded image would be tagged "Location A" if they are on the Location A page or any child pages.  

Thanks for the prompt response and taking the time to have a look at what I am trying to achieve.

Much obliged and Cheers!

Link to comment
Share on other sites

On 1/19/2021 at 9:57 AM, kongondo said:

Hi @StanLindsey,

I haven't seen that one before :-). Could you please tell me more about what's on that template? Assuming you have TD installed, could you please tell me/show me the output of the following?

Please add the following debug calls:


<?php
// around line #369 in the method ___render() in InputfieldMediaManager.module
bd($this->mediaManagerField, 'MEDIA MANAGER FIELD');

// around line #38 in the method __construct() in MediaManagerRender.php
bd($mediaManagerField,'MEDIA MANAGER FIELD');

edit: What's the name of your Media Manager Field?  Is it all lower_case?

Thanks.

Thanks Kongondo, this wasn't actually an issue with your module in the end. It was due to me trying to be clever and duplicating the ProcessPageEdit from /wire/ and making my own module based on it (in order to remove the bookmarks submenu from certain navigation items).

In the end i've just disabled bookmarks site wide and it all seems to work.

Link to comment
Share on other sites

1 hour ago, StanLindsey said:

Thanks Kongondo, this wasn't actually an issue with your module in the end. It was due to me trying to be clever and duplicating the ProcessPageEdit from /wire/ and making my own module based on it (in order to remove the bookmarks submenu from certain navigation items).

Thanks for reporting back :-).

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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • 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
       
×
×
  • Create New...