NC - Add one field to the "blog" plugin with specific requirements

Hello everyone,

it's me, the Elggnoob again. Sorry for bothering you with yet another noobish request.

I have no programming or IT background and I'm learning Elgg at the moment with the help of the manual, tutorials and Nikolai's tips he gave me on this website.

I've been able to adjust a good amount of points on my wishlist for my website, but there is one thing which I just can't do (yet). I think that I would be able to do this myself - in 2026, if I spend all my free time learning Elgg and PHP. Since I don't want to wait that long, I decided that I would ask someone to code this for me, so that I can get correct code and through it can learn how to do it myself next time.

This is just a hobby project for me. I have no budget for my website. But I'm willing to pay for people who do work for me. Since I don't have a clear idea how difficult my below stated wish would be to do (I imagine it's not too outlandish) and what the prices you guys ask, are, I kindly ask you to send me your offer(s). If it's within the price range I made up in my mind, I will gladly pay you for your help. If it's outside of my price range, I will have to play Lotto next week and hope for the best. ;)

My wish: Add one new field to the "blog" plugin with a specific customization of this field.

Details:

- In the full "blog" view:

          - The field's output shall show under the "description" area.

          - No special styling needed. (Same design as "description" area.)

          - The field shall only show in the "full view", not in the "brief view" in lists etc.

- In the "add" view:

          - The field shall show under the "description" area.

          - The field shall be a longtext field with a height of 3 lines.

          - The name of the field shall be "bandcamp_embed".

          - The title of the field shall say "Bandcamp widget (copy&paste your Bandcamp iframe code in here)." 

                    --> If this could be made translateable, that would be nice, but it doesn't have to be.

         - Crucial: Even though the field is a longtext, it needs a custom CKEditor style. The field needs to automatically start in "SourceEditing" mode (config.startupMode = 'source';) and there shall be no toolbar visible. (If "no toolbar" is not possible, then the only item in the toolbar shall be "SourceEditing".)

          - Add a check whether the input in the field includes the Bandcamp widget. If it has something else in it, then Elgg shall ignore the field (=show nothing for the field in the "full view"). I don't know how such a check could work, but at the least I imagine something like a check for the term "bandcamp.com" in the field.

Information 1: The only thing that shall be put into this field is the iframe embed code from Bandcamp. I need this extra field prepared for a direct copy&pasting, because, unfortunately, most of my users aren't able to manually click on "Source" in the "description" field. Thus I want to outsource this option to a place where my users don't have to do anything than copy&pasting the code they have.

Information 2: The bandcamp iframe embed widget already works on my website with the help of the "Elgg entities" plugin. Here is an example from my blog (you have to scroll down a bit until you see the widget):

https://www.dubbook.org/blog/view/435/tvs-greatest-dubs-s01e06-dub-rogue-cwazy-cupcakes-whim014

The Bandcamp widget's iframe embed code from the link above looks like this:

<iframe style="border-width:0;height:120px;width:100%;" src="https://bandcamp.com/EmbeddedPlayer/album=2780184875/size=large/bgcol=333333/linkcol=0f91ff/tracklist=false/artwork=none/transparent=true/" seamless=""><a href="https://whimsicalmusic.bandcamp.com/album/tvs-greatest-dubs-s01e06">WHIM014</a></iframe>

I'd hope that this could all be done within "my plugin" by overwriting the files from the original "blog" plugin. Please let me know if my wish is possible, if you can (and want to) do it, and how much it would cost me.

[NI] One bonus wish:

If we come to an agreement, could you mark (maybe with colors?) in your code all the areas that you changed compared to the original "blog" plugin code, so that I can learn what you did and (hopefully) be able to add more custom fields (e.g. for Soundcloud) myself in the future? I use "Notepad++" as text editor, in case this information helps. (And yes, my potential userbase would indeed need one field per possible embed option.)

Thank you for reading until here. I appreciate it.

Kind regards,

the Elggnoob

Professional Services

Professional Services

Get / offer professional help on Elgg; like customization, design, development, setup, hosting... Illegal trades are not allowed.