Hi,

The path to override default avatar for user is at:

/templates/<template_name>/html/com_easysocial/avatars/users/

You will have to mimic the sizes available at /media/com_easysocial/defaults/avatars/user/ where there are 4 sizes, large, medium, small, square.

This is the same for groups and events too.

Or you can go to ES backend > Profile Types > Avatars, Upload New Avatars, and then set the default. I believe this was added as of ES 1.3. See it in action here: http://www.test.alpineascent.com/members

Thanks for sharing this Josh By the way, Darko I am not really sure what you mean about the "fast paced releases", if you have added these overrides, the updates wouldn't actually mess up with your overriden avatars?

I could be wrong but this blog post http://stackideas.com/blog/easysocial-1-3-is-now-available shows that is published on Sept. 11 and im writing this 10 days later
In 10 days, we had 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4 = 5 upgrades.
Are you still not sure what im talking about with "fast paced upgrades"

The thing is i was always replacing avatars and covers in /media folders, i wasn't aware that avatars could be overriden in
/templates/<template_name>/html/com_easysocial/avatars/users/
because i couldnt really find any documentation about it, it would be a long shot to randomly guess the paths.
I hope it works with covers and groups /events too as well as other default images.


@Josh, thanks for advice, however, its not possible in my case.
I dont use any complicated profiling. I have only one (required) profile type and need only one default avatar.
Your solution will work for avatars, but not for covers, or group, event, default album, photo, category and other avatars and images.

Thats what im really hoping for Mark, an a way to upgrade without extra administration afterwards

Darko wrote:

In 10 days, we had 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4 = 5 upgrades.

Right, but they were minor releases with many fixes. This is one of the main reasons I typically avoid over rides unless there is no other way. CSS has been a huge asset in hiding/changing displays. ES is pretty flexible right now, in the future I wouldn't doubt that these little issues could be fixed without over rides.

Darko wrote:

Your solution will work for avatars, but not for covers, or group, event, default album, photo, category and other avatars and images.

Your absolutely right on this. I've had this in my mind for a while as well. The future of ES should eventually have default covers and defaults for other objects (events, groups, ect) without the need of replacing them manually.

Thanks for the heads up on this guys

Template overrides work for avatars but not for covers
Also, not for default photo or album images.
Not to mention font-icons used all over the place completely neglecting custom design as outlined in the screenshot.

Why did you make EasySocial so hard to customise?

And yeah, sorry to remind you but you haven't really looked into this either http://stackideas.com/forums/dark-theme-1
Im randomly finding white space all over "dark" theme, without even trying, so naturally, i need to use override because out of the box solution simply does not cut it.

Darko, I too was wanting classes for the stream icons. I'll be using articles a lot, yellow isn't really my color of choice.

@Josh, if it is just a color, then that's not a problem as fonticons work with CSS and you can change the color of it easily. Just inspect it.
The thing is, i wan't to make very specific icon set for niche site.

Lets say articles.
If you create a site for fishermans, you'd probably want to use an icon with a fish on the book, instead of just plain boring generic book fonticon.

Im not against using fonticons, but IMHO, the designers here went a bit too much.
Even a CSS sprite would be a better solution for native applications, and if a third-party wants to create it, have it as a separate image.
Its still one http request more per every image, i know, but hey, offer a bigger sprite with generic icons in it.

The bottom line, fonticon, though easy to implement and easier to maintain, work for generic blog sites, but for thematic, niche sites, they are overkill. And im sure the major focus of this extension should be on a niche site.

Thanks for the heads up on this Darko, we'll see what we can do about those icons in the future.

@Darko While there is no class for the icon itself, I discovered that one of the li elements give it a unique class which means we can style it however we want. I agree that a big part of ES's market should be niches. However what makes font icons great is how flexible they are in terms of manipulating things. With a few tweaks I could insert my own image sprites if I wanted.

Now here's a revolutionary idea, if ES had a image/icon manager that would be really cool. What it could do is change out stream icons, emoticons, site logo, default images, and ES icons through out the ES component. In addition to that a option could be made to toggle between font icons and small icons. If done right, it could make the site feel a lot more inclined to any particular niche. This would not only allow for site owners to more precisely design things, but cut out support time for the stacked team with the zillions of requests for icon/image mods.

How can i like the post above