By Gilles on Tuesday, 22 December 2015
Posted in General Issues
Replies 16
Likes 0
Views 396
Votes 0
Hi Folks,
The post notifications emails come with a "grey-ish" background colored div as seen in this code from such a notification:

<body style="background: #f4f3f1;">
<center style="background: #f4f3f1; padding: 30px 0">
<table border="0" cellpadding="0" cellspacing="0" style="color: #555; font: 16px/22px Arial, sans-serif; -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale;" width="600">
<tbody>
<tr>
<td style="background: #55585d; color: #fff; line-height: 1; font-size: 18px; font-weight: bold; text-align: center; padding: 30px;">
New Blog Post </td>
</tr>

<tr>


We need to change the bg color. Where do we change this?
I think it's the #55585d color we're looking to change... the one which creates the box around "New Blog Post"

Cheers
Hi Gilles,

Yes that is correct and the file can be found from your /components/com_easyblog/themes/wireframe/emails/html/post.new.php at line 15.
·
Tuesday, 22 December 2015 11:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks,
1. Does this mean the change would be overwritten when we next update EB?
2. Shouldn't such a branding colour be an option selectable in the configuration control panel?
Cheers,
G
·
Tuesday, 22 December 2015 20:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Gilles,

You can utilize the template overrides in EasyBlog without worrying about future upgrades. Copy the file that you want to modify into /templates/JOOMLA_TEMPLATE/html/com_easyblog/emails/html/

Adding a settings for these would not be justified as there are already a ton of settings that is in EasyBlog.
·
Tuesday, 22 December 2015 23:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,
Using an override here however means that any updates to the post.new.php code/file will be ignored, no?, including bug fixes and/or improvements, no?
·
Tuesday, 22 December 2015 23:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, that is correct So you need to monitor for changes when you upgrade.
·
Tuesday, 22 December 2015 23:31
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for confirming. Not ideal at all as I'm sure you'll agree. This is a recipe for a maintenance nightmare.

I understand you don't want to overcrowd the backend with config settings however, when it comes to colour schemes and branding, EB should offer a more suitable solution. In my opinion, it's a natural evolution of improving the product for EB customers.

Normally we have access to CSS for such customization but since there is no CSS available for the email message, a config setting would make sense. I'm certain I'm not unique in this view.
Food for thought.

Gilles
·
Tuesday, 22 December 2015 23:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Well, this is what we did for EasyBlog 5 and we had nightmare explaining each and every settings available

For instance, in EasyBlog 3.9 settings can only be configured globally and not per-menu basis. But we introduced more settings and more ways to configure the blog's layout via the menu only to realize that probably only < 1% of our customers actually use the menu extensively.

Let's see what we can do for the upcoming release
·
Wednesday, 23 December 2015 00:06
·
0 Likes
·
0 Votes
·
0 Comments
·
I understand.
Perhaps an "Advanced" section(s), could address this conundrum.
Thanks for listening.
G
·
Wednesday, 23 December 2015 00:13
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem, we'll see what we can do
·
Wednesday, 23 December 2015 00:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Mark, can you help out please?
I'm trying to determine which file exactly to edit. Which is is responsible to for generating the email notification?
and...
can you confirm that it should go exactly where you noted above?

I just don't want to have any surprises next time my client's site generates a post notification email.
Thanks
·
Wednesday, 23 December 2015 03:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Never mind... I hadn't scrolled back up sufficiently. I'll proceed as instructed unless you see an error in the instructions provided.
·
Wednesday, 23 December 2015 03:08
·
0 Likes
·
0 Votes
·
0 Comments
·
You would just need to copy the post.new.php file that Ezrul mentioned above into the folder /templates/JOOMLA_TEMPLATE/html/com_easyblog/emails/html/
·
Wednesday, 23 December 2015 12:29
·
0 Likes
·
0 Votes
·
0 Comments
·
Perfect. That's what I did. Let's hope the change will take effect.

By the way, since I need to copy and edit the file each time EB makes modifications to the original, what is the easiest, quickest method of knowing if the file has been revised when an EB update is issued by StackIdeas?
·
Wednesday, 23 December 2015 21:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Use a versioning system like git / mercurial. This way you can keep track of the changes that you did for your client and with such versioning system, you can also quickly revert back to previous commits

This is what we do for our customers who request customizations as well. Rather than charging them a maintenance fee every time, we educate them to use these tools so that they can save on their fee's and they have a full control of their own system
·
Wednesday, 23 December 2015 23:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark,
Git does sound interesting. However, there is a learning curve as I've never used it.
Until I do, can you recommend an alternate method? Does SI create release notes for example? where I could quickly see which files have been modified?
Other ideas?
Thanks,
G
·
Thursday, 24 December 2015 00:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Gilles,

Using git / mercurial is really pretty easy . As a web agency like yourself, I think you guys should start adapting to tools like this as it really makes your life much easier Anyway here's a guide, https://git-scm.com/

We do have a changelog / release notes but we don't actually have tracking of line changes yet (Something that I plan to enhance in the future) but you can find the changelog for EasyBlog at http://stackideas.com/changelog/easyblog

If you click on the "Modified files", it will display what files are modified for each commit
·
Thursday, 24 December 2015 12:58
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post