Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hello!
Just curious : are any future development planned for Shoutbox?
Thx.
Comment | File | Size | Author |
---|---|---|---|
#16 | shoutbox-migrateD7-2023731-16.patch | 89.88 KB | micahw156 |
#16 | interdiff-2023731-15-16.txt | 14.99 KB | micahw156 |
#15 | interdiff-2023731-14-15.txt | 2.68 KB | micahw156 |
#13 | interdiff-2023731-03-13.txt | 79.42 KB | happyhurricane |
Comments
Comment #1
vitalblue CreditAttribution: vitalblue commentedhi to all I'm planning to work on basic functionality of Drupal7 version and then think about the rest
thanks
Comment #2
Northern_Girl CreditAttribution: Northern_Girl commentedReady to make tests! :)
Comment #3
vitalblue CreditAttribution: vitalblue commentedfirst patch restore most of basic functionality
Comment #4
Brentnauer CreditAttribution: Brentnauer commentedWill this support OG?
Comment #5
vitalblue CreditAttribution: vitalblue commentedit is planned to support OG in the future too.
For the moment I'm working on basic functionality and the rest will follow
Comment #6
Anjaro CreditAttribution: Anjaro commentedHi, sounds good that there is being worked on this.
Im just a bit confused on how to proceed.
Do i install the old alpha or the dev and make the changes with the above patch ?
Or is it included in the dev ?
Thanks for any answer.
Comment #7
vitalblue CreditAttribution: vitalblue commentedhi Anjaro, still I don't have an answer for this patch.
I send a msg to disterics, owner of this module but I got no reply, for the moment.
I will let you know when this will be available in a new version.
Comment #8
vitalblue CreditAttribution: vitalblue commentedComment #9
vitalblue CreditAttribution: vitalblue commentedComment #10
micahw156@vitalblue - FYI, I just submitted a patch on #2103119: Configuration of Shoutbox not possible in D7 before I saw your patch from #3 above. Looks like the last patch committed on 7.x-1.x branch was over two years ago. Any word back yet from the maintainer?
I'll review your patch if I get a chance, but I'm in the middle of a big project right now and only had time to throw out a quick one-line fix for the config issue.
Comment #11
vitalblue CreditAttribution: vitalblue commentedHi micahw156, thanks for your response.
I didn't have any news from maintainer yet and still waiting for my patch.
I check the issue that you mentioned.
I have already change the path to admin/config/user-interface/shoutbox, but I don't have any problem to put that in "content" instead of "user-interface" level.
For the moment my aim is to resolve the maintenance problem of the module and then more patches will come.
Thanks
Comment #12
micahw156@vitalblue - I've uploaded a new patch to #2103119: Configuration of Shoutbox not possible in D7 using admin/config/user-interface/shoutbox instead.
Comment #13
happyhurricane CreditAttribution: happyhurricane commentedWorked with micahw156 to perform a coder review with the patch from #3 applied. Attaching new patch and interdiff for comparison.
Comment #14
happyhurricane CreditAttribution: happyhurricane commentedUploading correct patch file. Sorry.
Comment #15
micahw156Removed "info added by drupal.org packaging script" from .info files. This was added by the first patch, and should not be part of the git repository.
To be clear, the interdiff shows the changes between #14 and #15. The -15 patch is a diff against 7.x-1.x-dev (commit baee183).
We've put this work in a sandbox as the issue2023731 branch at https://bitbucket.org/hfccwebdev/module_shoutbox
(Also, fwiw, the bad upload patch on #13 was my fault.)
Comment #16
micahw156Removed LICENSE.txt file as mentioned in #1469876: Remove LICENSE.txt from Git repository.
Comment #17
micahw156@vitalblue: Also to clarify, there are no functional code changes between your -1 patch and the latest -16 patch. I haven't even looked at your code changes or enabled the module on a site yet. All we did today was run through coder module and clean up white spaces and comments as indicated by coder.
If you apply our changes and compare to your version using git diff -b you'll see exactly what we did here.
We will try to look at the code itself some time next week. Again, not really looking for a co-maintainer role, just trying to help get this patch commit ready.
@Anjaro: if you want to test with these patches, your best solution is to install git, then follow the instructions on the module's Version control page to clone the 7.x-1.x branch to your environment. Then download the latest patch and apply it using git apply.
Alternatively, you can use git to clone the sandbox I've created at https://bitbucket.org/hfccwebdev/module_shoutbox and check out the issue2023731 branch. I will continue to commit patches to that sandbox at least as long as I stay involved with this issue. If you really don't want to deal with git, you can test by downloading packages from the Downloads/Branches page on the Bitbucket repository.
Comment #18
Anjaro CreditAttribution: Anjaro commentedThanks
Sadly i dont have git, im on a hosted server and as i understand it, you have to have access to your own server to play with git ?
I will give a go on https://bitbucket.org/hfccwebdev/module_shoutbox/downloads
If no luck with this, im patience :) and i will hang on and wait to download the next version when available.
Thanks for your effort.
Comment #19
micahw156Marked #1798870: Getting together for a new version as duplicate of this issue.
Comment #20
micahw156@Anjaro,
You can install git locally. There are versions for Windows, Mac OS X and Linux. You can then use git to check out repositories, apply patches, etc, in your local environment, then transfer those files to your hosted server using normal means. However, if the downloads from bitbucket work for you, that's probably the easiest.
I highly, highly, highly recommend using git to manage revisions of the local copy of the files you're uploading to your host. If you've ever made a backup copy of a file before changing it, git is for you. Play with it for a couple of hours and you'll wonder how you ever lived without it.
Comment #21
micahw156Marked #1601150: Is this project still alive? as a duplicate of this issue.
Comment #22
Leeteq CreditAttribution: Leeteq commented@vitalblue; have you tried to follow this procedure, in case you want (co-)maintainership over this module?
"Dealing with unsupported (abandoned) projects"
https://drupal.org/node/251466
Comment #23
vitalblue CreditAttribution: vitalblue commentedHi Leeteq,
the ownership of this module passed to me few days ago.
I'm working now to release my first version this weekend.
Thanks for your help
Comment #24
Anjaro CreditAttribution: Anjaro commentedYES glad to hear that, Vitablue.
Comment #25
vitalblue CreditAttribution: vitalblue commentedpatch applied
thanks a lot