MyBB Hacks

If you have a link to the plugin, I might be able to look into it.

(06-02-2010 10:32 AM)ZiNgA BuRgA Wrote: [ -> ]If you have a link to the plugin, I might be able to look into it.

The very simple plugin coded by me, Yumi . It shows various buttons in postbit for certain usergroups and certain forum id(s) only, ignoring forum permission $forumpermissions and $fpermissions. So, I think it is not suitable for "general" forum. I think I should re-code it, so it can be used for other people

(06-02-2010 05:02 AM)leefish Wrote: [ -> ]HEADDESK.................gah....remember to check the plugins (4 hours of redoing templates )

Yup, that was the "problem"

I thought you are not serious to use that plugin. I'm really sorry, Lee I will re-code it and send it to you if you want it. My forum has been closed a few days ago.

Ah, yes. I think I have an idea with XThreads for games community forum. The basic idea is, our member can post their character in their game. They can take some screenshots related to their character in the game (e.g: their home, friends, family and etc), and upload it to their "Profile Thread" (I don't know what I should call it). They can update their "Profile Thread" whenever they want, e.g: if there is a change in their statistics. Here is an example for The Sims Game:

All the images and statistics in this screenshot is for example only, I didn't play that game recently

Hi RateU - the plug in wasn't the problem really - the problem was me being daft and not checking my plugins FIRST when I had a problem with the forum. That will teach me

The little screenshot is of course making my eyes gleam in happiness.....

I know Zinga asked if there was anything we would like to see as a future plug in etc - and you said custom profile fields. Looking at that screen shot gives me loads of ideas of how I would like to style profiles - I will go make my bid in the "anything you would like to maybe see added thread" .

And oh no on the forum closing - I liked your forum - and all the plug ins and the help - all gone..... Will you maybe put the plug ins up here (if Zinga allows it?)

(06-02-2010 08:59 PM)leefish Wrote: [ -> ]if Zinga allows it?

I think I've mentioned it before, but I really don't mind other people "taking over" this forum, as long as I get to keep my little corner here.  I don't really have much of a purpose for this site otherwise, so yeah, I don't care .

The screenshot comes from show thread page. But I don't have an idea how postbit, postbit_first and threadlist layout should be. I'm not a designer nor a coder

Update:
Using URL (HTTP/S) Text Mask Filter preset for Textbox for Developer Website:
Edit textbox for Developer Website custom thread fields (#3 field):
Text Mask Filter: URL (HTTP/S)

I have an idea, and I think I can use this example application for this purpose.

In the next XThreads version, v 1.4, XThreads supports language prefix. It means, if we want to change some default words to make it suitable for our application, we don't need to type it manually in our template. It will make XThreads more flexible and dynamic, especially if we have a non English forum, or, we want to change some custom thread fields from one of our XThreads application to other purpose. So, I think it is better if we make the custom thread fields title more "dynamic" too.

Right now, using this example applications as sample, I have an idea like this:

We need to edit these custom thread fields:

1. Textbox for Product Name:
   Display Format:
   
   Code:

   <setvar pfname>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfname']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfname']} variable in our template.
   With this way, when we change the title of this field via Custom Thread Fields Edit Page, we don't need to change it in our template. The variable will "update" it automatically.
   
   We will do the same thing with other custom thread fields.

2. Textbox for Developer:
   Display Format:
   
   Code:

   <setvar pfdev>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfdev']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfdev']} variable in our template.

3. Textbox for Product Version:
   Display Format:
   
   Code:

   <setvar pfversion>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfversion']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfversion']} variable in our template.

4. Textbox for Release (Year):
   Display Format:
   
   Code:

   <setvar pfrealese>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfrealese']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfrealese']} variable in our template.

5. Multiline Textbox for Product Description:
   Display Format:
   
   Code:

   <setvar pfdesc>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfdesc']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfdesc']} variable in our template.

6. Listbox for Categories:
   Display Format:
   
   Code:

   <setvar pfcat>htmlspecialchars_uni($GLOBALS['threadfield_cache']['pfcat']['title'])</setvar> {VALUE}

   ---

   For displaying this custom thread field title, we need to put {$GLOBALS['tplvars']['pfcat']} variable in our template.
   
   

Now, we need to edit some template, replacing the previous manual typed thread fields title with the variable above:

1. pf_forumdisplay_thread
   
   HTML Code

   <table border="0" cellspacing="{$theme['borderwidth']}" cellpadding="{$theme['tablespace']}" width="100%"> <tr> <td> <table border="0" cellspacing="{$theme['borderwidth']}" cellpadding="{$theme['tablespace']}" class="tborder" style="clear: both;"> <tr> <td class="thead" align="center" colspan="{$colspan}"> <div><strong><a href="{$thread['threadlink']}" class="{$inline_edit_class} {$new_class}" id="tid_{$inline_edit_tid}">{$thread['subject']}</a></strong></div> </td> </tr> <tr> <td class="{$bgcolor}" width="1"> <div align="center"> <img src="{$GLOBALS['threadfields']['pfpic']['url']}/thumb320x240" alt="{$thread['subject']} Screenshot" title="{$thread['subject']} Screenshot" width="{$GLOBALS['threadfields']['pfpic']['thumbs']['320x240']['w']}" height="{$GLOBALS['threadfields']['pfpic']['thumbs']['320x240']['h']}" /> </div> </td> <td class="{$bgcolor}" width="100%"> <table border="0" width="100%"> <tr> <td valign="top" width="120">{$GLOBALS['tplvars']['pfname']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['GLOBALS['tplvars']']['pfname']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfdev']}</td> <td width="1" valign="top">:</td> <td valign="top"><a href="{$GLOBALS['threadfields']['pfdevurl']}">{$GLOBALS['threadfields']['pfdev']}</a></td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfversion']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfversion']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfrealese']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfrealese']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfcat']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfcat']}</td> </tr> {$rating} <tr> <td valign="top">{$lang->author}</td> <td width="1" valign="top">:</td> <td valign="top">{$thread['profilelink']}</td> </tr> <tr> <td valign="top">{$lang->views}</td> <td width="1" valign="top">:</td> <td valign="top">{$thread['views']}</td> </tr> <tr> <td valign="top">{$lang->replies}</td> <td width="1" valign="top">:</td> <td valign="top"><a href="javascript:MyBB.whoPosted({$thread['tid']});">{$thread['replies']}</a>{$unapproved_posts}</td> </tr> </table> </td> {$modbit} </tr> </table> </td> <td>&nbsp;</td> <td valign="top" width="30%"> <table border="0" cellspacing="{$theme['borderwidth']}" cellpadding="{$theme['tablespace']}" class="tborder" style="clear: both;"> <tr> <td class="thead" align="center" colspan="{$colspan}"> <div><strong>{$GLOBALS['tplvars']['pfdesc']}</strong></div> </td> </tr> <tr> <td valign="top" class="{$bgcolor}" width="300"> <div style="text-align: justify; padding: 3px;"> <span class="float_left" style="margin: 5px 5px 0px 0px;"> <img src="{$GLOBALS['threadfields']['pfpic']['url']}/thumb88x66" alt="{$thread['subject']} Screenshot" title="{$thread['subject']} Screenshot" width="{$GLOBALS['threadfields']['pfpic']['thumbs']['88x66']['w']}" height="{$GLOBALS['threadfields']['pfpic']['thumbs']['88x66']['h']}" /> </span> {$GLOBALS['threadfields']['pfdesc']} </div> <br class="clear" /> <span class="float_right smalltext"> <em><a href="{$thread['lastpostlink']}">{$lang->lastpost}</a>: {$lastposterlink}, {$lastpostdate} {$lastposttime}</em> </span> <br class="clear" /> <span class="float_right smalltext"> <img src="{$theme['imgdir']}/{$folder}.gif" alt="{$folder_label}" title="{$folder_label}" /> {$icon}{$prefix}{$gotounread} </span> </td> </tr> </table> </td> </tr> </table> <br />

   ---

2. pf_postbit_first
   
   HTML Code

   {$ignore_bit} <a name="pid{$post['pid']}" id="pid{$post['pid']}"></a> <table border="0" cellspacing="{$theme['borderwidth']}" cellpadding="{$theme['tablespace']}" class="tborder" style="{$post_extra_style} {$post_visibility}" id="post_{$post['pid']}"> <tbody> <tr> <td class="tcat"> <div class="float_left smalltext"> {$post['postdate']}, {$post['posttime']} <span id="edited_by_{$post['pid']}">{$post['editedmsg']}</span> </div> {$post['posturl']} </td> </tr> <tr> <td class="trow1 {$unapproved_shade}"> <table cellspacing="0" cellpadding="0" border="0" style="width: 100%;"> <tr> <td class="post_avatar" width="1" style="{$post['avatar_padding']}"> <img src="{$GLOBALS['threadfields']['pfpic']['url']}/thumb160x120" alt="" title="{$GLOBALS['threadfields']['pfname']}" /> </td> <td class="post_author"> <table border="0" width="100%" class="smalltext"> <tr> <td valign="top">{$GLOBALS['tplvars']['pfname']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfname']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfdev']}</td> <td width="1" valign="top">:</td> <td valign="top"><a href="{$GLOBALS['threadfields']['pfdevurl']}">{$GLOBALS['threadfields']['pfdev']}</a></td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfversion']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfversion']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfrealese']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfrealese']}</td> </tr> <tr> <td valign="top">{$GLOBALS['tplvars']['pfcat']}</td> <td width="1" valign="top">:</td> <td valign="top">{$GLOBALS['threadfields']['pfcat']}</td> </tr> <tr> <td valign="top">Posted By</td> <td width="1" valign="top">:</td> <td valign="top">{$post['profilelink']}</td> </tr> </table> </td> </tr> </table> </td> </tr> <tr> <td class="trow2 post_content {$unapproved_shade}"> <div class="largetext" align="center"><strong>{$post['subject']}</strong></div> <div class="post_body" id="pid_{$post['pid']}"> {$post['message']} </div> {$post['attachments']} {$post['signature']} <div class="post_meta" id="post_meta_{$post['pid']}"> {$post['iplogged']} </div> </td> </tr> <tr> <td class="trow1 post_buttons {$unapproved_shade}"> <div class="author_buttons float_left"> {$post['button_email']}{$post['button_pm']}{$post['button_www']}{$post['button_find']} </div> <div class="post_management_buttons float_right">{$post['button_edit']}{$post['button_quickdelete']}{$post['button_quote']}{$post['button_multiquote']}{$post['button_report']}{$post['button_warn']}{$post['button_reply_pm']}{$post['button_replyall_pm']}{$post['button_forward_pm']}{$post['button_delete_pm']} </div> </td> </tr> </tbody> </table>

   ---

I didn't update the first post, because I need to know whether it is OK or not to use it
The Live Demo for this application already use the code above.

Yeah, I might make it easier to reference the title in the next version.
I've been musing over the possibility of a {$threadfields_x['key']['thing']} type variable.  "title" could be a "thing".  Maybe stick a few other things in there, like matched components of the text mask or similar in there.  Maybe even a secondary display format?

can anyone create this as a mod?????

(11-09-2010 05:04 AM)RateU Wrote: [ -> ]Update:
Using URL (HTTP/S) Text Mask Filter preset for Textbox for Developer Website:
Edit textbox for Developer Website custom thread fields (#3 field):
Text Mask Filter: URL (HTTP/S)

Getting Error:

Invalid value supplied for "Developer Website".

Did i have to change anything in the "Display Format" ?

Have tested sone things but I found no fix.