Leaderboard

Hai Webflake, Just a quick post regarding our "Site Feedback, Ideas & Questions" forum. As many of you know, since we updated to version 4 of IP.Board, we have made use of a tracker which can be found on the navigation bar above to log site bugs and suggestions which will enable us to set priority levels and progression of site updates. "Site Feedback, Ideas & Questions" forum has been changed to "Site Questions" If you have any question regarding WebFlake, it should now be posted there.Site suggestions should now be submitted to the tracker here.Site issues and bugs should now also be submitted to the tracker here.Newly submitted items on the tracker will now appear in the "Latest Bugs & Suggestions" sidebar on the board index. Please consider the following as a guideline on trying to present new ideas to the community and Staff of WebFlake. (Credit to Davlin) Present the problem: What do you currently feel is an issue or inadequate on WebFlake? Why is it a problem? Why is this something that should be added, removed or changed in some way on WebFlake? Present a solution to the problem: Give a concrete solution to the problem, include hypothetical examples and scenarios to exemplify the effectiveness of said solution. Consider drawbacks of solution: Hypothesize on some of the negative impacts of your solution, perhaps extrapolate some potential remedies to these drawbacks. Some basic tips: Check submited suggestions! If your suggestion has already been offered, do not submit it again. If you have ideas for modifying that suggestion, submit them to the original topic.Utilize appropriate titles! Please do not title your topic "feedback", "ideas" or anything generic. Be as descriptive as possible.Not all ideas will be approved! Sometimes users, even though they mean well, will offer ideas that are just plain.. useless. Threads like these will often receive a simple "this will not happen" sort of response from Staff and then be locked. This isn't because we don't like you, or hate your ideas.. we just don't like that one in particular. Submit others!Be constructive! I place particular emphasis on this one as far too many members have been offering feedback on features with "this is dumb" comments or deliberate bashing of our Staff team. Topics/posts like these will be removed at the discretion of Staff. Anything particularly vulgar or aggressive in nature can result in account action(s). If you have any suggestions, please don't hestitate to add them to the tracker. Much appreciated, WebFlake Staff

Step:1 Go to ACP > Customization > Themes and Select the skin you wish to edit Step: 2 Find postContainer in the templates Step: 3 Look for <li class='cAuthorPane_photo'> {template="userPhoto" app="core" group="global" params="$comment->author(), 'large', $comment->warningRef()"} </li> Step: 4 Replace it with <li class='cAuthorPane_photo'> {template="userPhoto2" app="core" group="global" params="$comment->author(), 'variable', $comment->warningRef()"} </li> Step: 5 Create New HTML Template Name: UserPhoto2 Variables: $member, $size='small', $warningRef=NULL, $classes='', $hovercard=TRUE Location: Add To an existing location Existing Location: front Group: Add to an existing group Existing Group: global Application: System Step 6: Find HTML template "UserPhoto2" and paste the following code into it {{if $member->member_id and \IPS\Member::loggedIn()->canAccessModule( \IPS\Application\Module::get( 'core', 'members' ) )}} {{$memberURL = ( $warningRef ) ? $member->url()->setQueryString( 'wr', $warningRef ) : $member->url();}} <a href="{$memberURL}" {{if $hovercard}}data-ipsHover data-ipsHover-target="{$memberURL->setQueryString( 'do', 'hovercard' )}"{{endif}} class="ipsUserPhoto ipsUserPhoto_{$size}{{if $classes}} {$classes}{{endif}}" title="{lang="view_user_profile" sprintf="$member->name"}"> <img src='{{if $member->pp_main_photo}}{file="$member->pp_main_photo"}{{else}}{file="$member->photo"}{{endif}}' alt='{$member->name}'> </a> {{else}} <span class='ipsUserPhoto ipsUserPhoto_{$size} {{if $classes}}{$classes}{{endif}}'> <img src='{file="$member->photo"}' alt='{$member->name}'> </span> {{endif}} Step: 7 Find custom.css and Add this line of code below .ipsUserPhoto_variable img, img.ipsUserPhoto_variable, .ipsUserPhoto_variable:after { width: 170px; {{if theme.rounded_photos}} border-radius: 0px; {{endif}} } after you have completed all the steps above the results should be like this below

The question(s) in this support topic have been answered and the owner has been able to solve the problem. Because of this, the support topic has been closed and moved. If you have other questions, please open a new topic.

​No, I doubt it'll happen as this is done for a reason. And since this request has been filled, this will now be locked.

Are you talking about making them larger, if so then this thread may help... http://webflake.sx/topic/14959-larger-avatars-in-post/

It's defined per group now in the ACP of IPB 4. ACP -> Members -> Groups -> (group) / Edit -> Social Hope I helped!

​edited the code a bit read Step:4 above and it should work now

The question(s) in this support topic have been answered and the owner has been able to solve the problem. Because of this, the support topic has been closed and moved. If you have other questions, please open a new topic.

changing your language file would change it site wide whereever the word forum is used or the {{language_forum}}.

sitting right here http://webflake.sx/topic/14800-remove-forums-title-name-on-top-of-categories/

When requesting logos, please do not post a topic with "hey, I'm new, make me a logo". Try to elaborate and offer some details on what you'd like the logo to be. Most designers here simply won't have any interest in creating a logo only for it to be passed up by the requester because it didn't meet their standards. Suggested information: Color Scheme Font type (DaFont.com) Images Community type (gaming/design/fansite) Logo size Text desired Example logo Slogan (if applicable) Animation (if applicable) Here's an example logo request: The above example includes most of the suggested variables for the request. Logo requests that are vague will be locked/discarded.