Jump to content

Recommended Posts

HELLO!

I've been working on a user messaging module which I am nearly ready to release as version 1.

Currently I have the below functionality and I'm looking for feedback to what other things may be useful for people looking to add user to user messaging on their sites.

  • compose message to one or more users known to PW
  • js to enable tag based UI display of user names input on compose message form
  • display all message threads with reply forms
  • reply to message thread displaying each user name by each message in the thread
  • display "unread" when a thread has new content that hasnt been seen by current user
  • delete or unpublish message thread (configurable)
  • display total message thread count
  • display total unread threads (threads that have new replies that the current user has not seen)
  • delete all message threads and associated data (not meant for the users to have access to)

road map

  • send email to user on new message to a thread they are included in
Edited by benbyf
title typo
  • Like 8

Share this post


Link to post
Share on other sites

Hi @benbyf

What is "Memebers"? ;) Jokes aside, I would love to see "shared message boards", seen by defined group members (roles), so that site editors/administrators can send/discuss important messages in order to better collaborate, say on a dashboard which loads first when logging into admin. Does your module support something like that? I cannot seem to decipher this from your description above. 

Thanks in advance, BTW, sounds like a nice module anyway.

Edited by szabesz
typos
  • Like 1

Share this post


Link to post
Share on other sites

@szabesz Thanks, not sure I understand fully you requirements, like a "message the site admin" area?

  • Like 1

Share this post


Link to post
Share on other sites

Well, I'd better show an example, I guess. Something like this:

http://www.theblog.ca/wordpress-post-notes

On the WP dashboard there is a "collaboration notes made by others" and underneath there is an AXAJ form to add more notes. It is like a simple message board when used with this simple setup. This WP plugin has more to it than a "global" message board, but I've never tried those features. Most of the time a simple FB like flow of conversation is enough when only a few editors are using a site.

Maybe your module is not about such a feature?

Edited by szabesz
typo
  • Like 1

Share this post


Link to post
Share on other sites

@szabesz not what i intended, but probably not a long shot to create a mini module using the messaging but in the admin to be viewed by all users with the permissions. will look into it after I've published the main messaging module. Thanks

  • Like 1

Share this post


Link to post
Share on other sites

Sorry this has been on hiatus as i've had lots of work on and had to build a shop from the ground up in order to sell it :/

Share this post


Link to post
Share on other sites

Anyone still interested in this module?

Also the module saves all messages in plain text, would you be interested in a encrypted version of the module using key exchange or hash keys?

 

  • Like 2

Share this post


Link to post
Share on other sites

Have to take a look, but messaging sounds great! encrypted would be nice!

What's with group messages oder push notifications (web push)?

  • Like 1

Share this post


Link to post
Share on other sites

Hi Ben,

19 hours ago, benbyf said:

Anyone still interested in this module?

I'm still interested as long as it is also about admin side messaging out of the box.

  • Like 2

Share this post


Link to post
Share on other sites
7 hours ago, szabesz said:

Hi Ben,

I'm still interested as long as it is also about admin side messaging out of the box.

Do you mind giving me a description of your use case, look back over your comments but still cant quite get my head around it.

  • Like 1

Share this post


Link to post
Share on other sites
6 hours ago, benbyf said:

a description of your use case

Maybe watching something similar helps: https://www.youtube.com/watch?v=_d0hZ8iS344

I'm thinking of logged in users being able to post messages in the PW backend which supports remote collaboration, or support developers by providing some means to announce changes made to the site. Currently if users want to communicate, PW does not support them at all.

 

  • Like 2

Share this post


Link to post
Share on other sites
On 2/19/2019 at 8:26 PM, szabesz said:

Maybe watching something similar helps: https://www.youtube.com/watch?v=_d0hZ8iS344

Seems pretty straightforward especially if capturing flow of conversation is not important. If that is a requirement, maybe Comments module (or borrowing from it) would cut it? Just wondering out loud...

  • Thanks 1

Share this post


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

If that is a requirement, maybe Comments module (or borrowing from it) would cut it?

I think so, making use of the Comments module sounds like a really good idea. The youtube link I posted was just about the "dashboard like" behavior but besides being able to post announcements some simple conversation would be nice to have too.

Share this post


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

The youtube link I posted was just about the "dashboard like" behavior but besides being able to post announcements some simple conversation would be nice to have too.

Not wanting to go OT here, if this is the case, I'm wondering if this is better off as a separate/standalone module (so, new topic 😉) from what is described in the first post of this thread?

 

EditHmm..Or maybe what you describe falls within the remit of what the module in this thread is about? I think am just confusing myself now. Anyway, let me know...

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites
On 2/23/2019 at 10:48 PM, kongondo said:

EditHmm..Or maybe what you describe falls within the remit of what the module in this thread is about? I think am just confusing myself now. Anyway, let me know...

I think Ben's "specification" is just somewhat vague so that is the source of our confusion. Anyway, Members Messaging can be either for frontend or PW's backend or even for both but in the latter case it would probably be practical to split the code among "submodules".

  • Like 2

Share this post


Link to post
Share on other sites
14 hours ago, szabesz said:

I think Ben's "specification" is just somewhat vague so that is the source of our confusion. Anyway, Members Messaging can be either for frontend or PW's backend or even for both but in the latter case it would probably be practical to split the code among "submodules".

Module was created to track date/time based messages between one or more users. That said it might be I could use it to create a new module that has an admin page that acts as a conversation between the logged in user and the admin or any other users.

If you're looking for a less structured, freeform notes sort of collaboration thing then let me know and ill have a think.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the additional explanation!

I am after something like this:

22 hours ago, benbyf said:

That said it might be I could use it to create a new module that has an admin page that acts as a conversation between the logged in user and the admin or any other users.

Share this post


Link to post
Share on other sites

That would be fun to build! 🙂 If only I had time for it...

  • Like 1

Share this post


Link to post
Share on other sites
19 hours ago, szabesz said:

I am after something like this:

 

1 hour ago, bernhard said:

That would be fun to build! 🙂 If only I had time for it...

I had a stab at this over the weekend (during my free time, ahem).  I'm finalising it now. Hope to post alpha(-ish) version tonight. I'll start a separate thread.

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites
On 2/27/2019 at 4:09 PM, kongondo said:

 

I had a stab at this over the weekend (during my free time, ahem).  I'm finalising it now. Hope to post alpha(-ish) version tonight. I'll start a separate thread.

WIP here:

 

  • Like 1

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...