Jump to content

Members Messaging


benbyf
 Share

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
Link to comment
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
Link to comment
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
Link to comment
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
Link to comment
Share on other sites

  • 2 months later...
  • 1 year later...
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
Link to comment
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
Link to comment
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
Link to comment
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.

Link to comment
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
Link to comment
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
Link to comment
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
Link to comment
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.

Link to comment
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
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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Similar Content

    • By monollonom
      PageMjmlToHtml
      Github: https://github.com/romaincazier/PageMjmlToHtml
      Modules directory: https://processwire.com/modules/page-mjml-to-html/
      A module allowing you to write your Processwire template using MJML and get a converted HTML output using MJML API.
      This is considered to be in alpha and as such needs some testing before being used in production!

      About
      Created by Mailjet, MJML is a markup language making it a breeze to create newsletters displayed consistently across all email clients.
      Write your template using MJML combined with Processwire’s API and this module will automatically convert your code into a working newsletter thanks to their free-to-use Rest API.
      Prerequisite
      For this module to work you will need to get an API key and paste it in the module’s configuration.
      Usage
      Once your credentials are validated, select the template(s) in which you’re using the MJML syntax, save and go visualize your page(s) to see if everything’s good. You will either get error/warning messages or your email properly formatted and ready-to-go.
      From there you can copy/paste the raw generated code in an external mailing service or distribute your newsletter using ProMailer.
      Features
      The MJML output is cached to avoid repetitive API calls Not cached if there are errors/warnings Cleared if the page is saved Cleared if the template file has been modified A simple (dumb?) code viewer highlights lines with errors/warnings A button is added to quickly copy the raw code of the generated newsletter Not added if the page is rendered outside of a PageView Only visible to users with the page’s edit permission A shortcut is also added under “View” in the edit page to open the raw code in a new tab Multi-languages support
      Notes
      The code viewer is only shown to superusers. If there’s an error the page will display:
      Only its title for guests Its title and a message inviting to contact the administrator for editors If you are using the markup regions output strategy, it might be best to not append files to preserve your MJML markup before calling the MJML API. This option is available in the module’s settings.
    • By Marco Ro
      Hi guys!
      I'm a bit anxious because this is the first module I present! (beta modulo) But I will finally be able to share something with the community too! :)
      This is a BETA version of the PayPal payment system called: PayPal Commerce Platform.
      It is an advanced system (Business Pro account is needed) that brings various benefits in terms of fees and above all integrates direct payment with credit/debit cards. 
      The module integrates with Padloper 0.0.2, which is the current installation I'm using.
      This system integrates the classic PayPal buy button, the alternative or local payment method and the new payment system: credit/debit cards that doesn't go through the PayPal account. It is a Stripe-style payment, it connects directly with the bank and integrates 3D security validation.
      I say that it is a BETA because this module currently only works with Sandbox account, to put it live you need to change API url manually (manually for the moment).
      Because this module is not ready for live:
      I would like to have your opinion on how I built the module (is the first one I do). I don't want to share something that is not fish but I need a comparison with someone more experienced than me, for be sure that this is the best way to code the module.
      If you want to try this I created a git, you will find all the instructions for installation and correct operation. (Git has a MIT licensed)
      https://github.com/MarcooRo/processwire-PayPal-Commerce-Platform I hope I did something that you guys can like :)
    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      FieldtypeQRCode
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      A simple fieldtype generating a QR Code from the public URL of the page, and more.
      Using the PHP library QR Code Generator by Kazuhiko Arase.

      Options
      In the field’s Details tab you can change between .gif or .svg formats. If you select .svg you will have the option to directly output the markup instead of a base64 image. SVG is the default.
      You can also change what is used to generate the QR code and even have several sources. The accepted sources (separated by a comma) are: httpUrl, editUrl, or the name of any text/URL/file/image field.
      If LanguageSupport is installed the compatible sources (httpUrl, text field, ...) will return as many QR codes as there are languages. Note however that when outputting on the front-end, only the languages visible to the user will be generated.
      Formatting
      Unformatted value
      When using $page->getUnformatted("qrcode_field") it returns an array with the following structure:
      [ [ "label" => string, // label used in the admin "qr" => string, // the qrcode image "source" => string, // the source, as defined in the configuration "text" => string // and the text used to generate the qrcode ], ... ] Formatted value
      The formatted value is an <img>/<svg> (or several right next to each other). There is no other markup.
      Should you need the same markup as in the admin you could use:
      $field = $fields->get("qrcode_field"); $field->type->markupValue($page, $field, $page->getUnformatted("qrcode_field")); But it’s a bit cumbersome, plus you need to import the FieldtypeQRCode's css/js. Best is to make your own markup using the unformatted value.
      Static QR code generator
      You can call FieldtypeQRCode::generateQRCode to generate any QR code you want. Its arguments are:
      string $text bool $svg Generate the QR code as svg instead of gif ? (default=true) bool $markup If svg, output its markup instead of a base64 ? (default=false) Hooks
      Please have a look at the source code for more details about the hookable functions.
      Examples
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $page = $event->arguments("page"); $event->return = $page->title; // or could be: $event->return = "Your custom text"; }) $wire->addHookAfter("FieldtypeQRCode::generateQRCodes", function($event) { $qrcodes = $event->return; // keep everything except the QR codes generated from editUrl foreach($qrcodes as $key => &$qrcode) { if($qrcode["source"] === "editUrl") { unset($qrcodes[$key]); } } unset($qrcode); $event->return = $qrcodes; })
    • By Sebi
      AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api. 
      This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
      Features
      You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
      The GET-param "file" defines the basename of the file which you want to get.
      The following GET-params (optional) can be used to manipulate an image:
      width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
    • By MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
×
×
  • Create New...