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 7

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

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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...