DevFuse Forums - Tutorials

Fatal error on install

Wed, 16 Nov 2011 03:49:20 +0000

If you get a fatal error when first installing an application, the most common cause is a bug with IPB 3.x that doesn't insert the application templates when installing therefore triggering an error.

Example of this error:

Quote

Fatal error: Call to a member function templateFunctionName() on a non-object in /the/file/location/file.php on line 555

The error won't always be the same as above but you get the idea. Another symptom may be a blank/white page rather then the error. You can find bug reports on the IPS Bug Tracker here and here. As of IPB 3.2.3 this still appears to be a problem and goes back to IPB 3.0.x. Below is an IPS provided fix if you have this problem.

Manual Fix: (Provided by IPS)

Quote

Here's a work-around.

1) Make some skin OTHER than IP.Board the default skin, using the blue HTML icons in ACP -> Look & Feel.
2) Edit the settings for the IP.Board skin. The skin key field should show up, and it will likely be blank. Fill in the value: default
3) save the IP.Board skin.
4) Now use those HTML icons to make IP.Board the default if you want to, but you can leave it at whichever default skin you wish.
5) Go to ACP -> Look & Feel -> Template Tools -> Rebuild Master Skin Data -> select all the checkboxes in that section -> click the Rebuild button.

That will at least get the skin key set properly, which you can check in the ibf_skin_collections table of the database. The IP.Board skin should show the value 'default' in the 'set_key' field for the IP.Board skin entry. If it's there, that should resolve the problem going forward.

If you installed a new app shortly before fixing the underlying problem, and if it's not in heavy use yet, just uninstall and reinstall it. That should work, but if it doesn't for you, please file a support ticket.

As mentioned above, if new install then an uninstall and re-install with the provided instructions followed will work. But if you've upgraded or already have data added, please submit a support ticket with admin and ftp login details as the fix needs to be applied manually and is more complex.

3.2.x Add one or more custom block in sidebar

Mon, 07 Nov 2011 07:47:11 +0000

As you all know you can add some automatic or custom content in the sidebar of the board index of IPB 3.2
To insert new custom blocks you can use the classical (e32)Custom Sidebar Blocks 1.5.0 http://community.inv...sidebar-blocks/ that allows you to insert one or more custom blocks in sidebar, but all these will be displayed next to each other, and not interspaced with other automatic blocks.
With a manual edit of template you can put at least another 2 blocks, one or more blocks in the sidebar above all, and one or more below all.

Look&Feel - Manage Skin Sets & Templates - your skin - boardindexTemplate

Findi this:

   		    
                {$block}

and add BEFORE and or AFTER:



    TITLE
    
        MESSAGGIO HTML  MESSAGGIO HTML MESSAGGIO HTML

3.2.x Adjust the log pruning schedule

Sun, 06 Nov 2011 13:26:35 +0000

IP.Board provides options (System Settings > Advanced > Log Pruning) to enable / disable pruning various logs such as spider logs, database error logs, spam logs etc.

The only issue some administrators may have is that thirty days may be too long, or in some rare cases not enough but again not enough to justify not pruning them.

A simple tweak is possible to adjust the pruning schedule.

Connect via FTP or your hosts file manager and open admin/applications/core/tasks/logprune.php

Around line 34, find...

protected $deleteTime = 2592000;

Replace that line with one of the following, depending on what you require.

14 days

protected $deleteTime = 1209600;

7 days

protected $deleteTime = 604800;

3 days

protected $deleteTime = 259200;

Save the change. The settings description will still indicate 30 days but the actual pruning will take place at the days interval you have specified. , remember this change will effect them all so you may wish to disable any pruning you do not want to occur at that interval.

3.2.x Public polls by default

Sat, 29 Oct 2011 10:51:54 +0000

Here is a quick, simple tutorial on how to have "Make votes public?" checked by default. This may eliminate the problem of members who do wish to have a public poll but are unable to change it after submitting it.

A small skin edit is required.

ACP > Look / Feel > Skin Manager > (choose skin) > Manage Templates / CSS > Post Screen > Poll Box >

Find...


                        checked='checked' />
                        {$this->lang->words['poll_fs_public']}

Change to...


                        checked='checked' />
                        {$this->lang->words['poll_fs_public']}

Save the change. Repeat for other skins if required. Quick pic:

3.2.x Adding joined date to topic view

Wed, 28 Sep 2011 10:29:00 +0000

Its very easy with a small skin edit to add the joined date back to topic view on 3.2 if you require it.

ACP > Look / Feel > Skin Manager > (choose skin) > Manage Templates / CSS > Global Templates > UserInfoPane

Find...

        
   	     {parse expression="$this->registry->getClass('class_localization')->formatNumber( intval( $author['posts'] ) )"} {$this->lang->words['m_posts']}

Add this after the tag but before the tag...

{$this->lang->words['m_joined']} {parse date="$author['joined']" format="joined"}

So you end up with this:

        
   	     {parse expression="$this->registry->getClass('class_localization')->formatNumber( intval( $author['posts'] ) )"} {$this->lang->words['m_posts']}
        
        
{$this->lang->words['m_joined']} {parse date="$author['joined']" format="joined"}

Save. Quick pic:

You might want to add a
tag or suchlike to space it out, but that's essentially it.

Different bbcode quote in standard 3.2.0 skin

Wed, 27 Jul 2011 12:55:59 +0000

I think that quote bbcode in standard 3.2.0 skin is not the bast, because it's not very different from normal post.

To make it more visible but a with little dimension you can open your skin, css, ipb_common.css and find this:

/* Quote boxes */

p.citation {
	font-size: 12px;
	padding: 8px 10px;
	border-left: 2px solid #989898;
	/*background: #f3f3f3 */
	background: #f6f6f6;
	background: -moz-linear-gradient(top, #f6f6f6 0%, #e5e5e5 100%); /* firefox */
	background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#f6f6f6), color-stop(100%,#e5e5e5)); /* webkit */
	border-top: 2px solid #e5e5e5;
	border-right: 2px solid #e5e5e5;
	-moz-border-radius: 5px 5px 0 0;
	-webkit-border-radius: 5px 5px 0 0;
	border-radius: 5px 5px 0 0;
	font-weight: bold;
}

div.blockquote {
	font-size: 12px;
	padding: 10px;
	border-left: 2px solid #989898;
	background: #fdfdfd;
	border-right: 2px solid #e5e5e5;
	border-bottom: 2px solid #e5e5e5;
	-moz-border-radius: 0 0 5px 5px;
	-webkit-border-radius: 0 0 5px 5px;
	border-radius: 0 0 5px 5px;
	background: #f7f7f7;
}

and replace with

/* Quote boxes */
p.citation {
	font-size: 11px;
	padding: 5px 5px;
	border-left: 2px solid #989898;
	/*background: #f3f3f3 */
	background: #b1b2b2;
	background: -moz-linear-gradient(top, #f6f6f6 0%, #b1b2b2 100%); /* firefox */
	background: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#f6f6f6), color-stop(100%,#e5e5e5)); /* webkit */
	border-top: 2px solid #e5e5e5;
	border-right: 2px solid #e5e5e5;
	-moz-border-radius: 5px 5px 0 0;
	-webkit-border-radius: 5px 5px 0 0;
	border-radius: 5px 5px 0 0;
	font-weight: bold;
}

div.blockquote {
	font-size: 10px;
	padding: 5px;
	border-left: 2px solid #989898;
	background: #e9eaea;
	border-right: 2px solid #e5e5e5;
	border-bottom: 2px solid #e5e5e5;
	-moz-border-radius: 0 0 5px 5px;
	-webkit-border-radius: 0 0 5px 5px;
	border-radius: 0 0 5px 5px;
}

Result:

3.2.x Adjusting status update numbers

Tue, 26 Jul 2011 14:39:48 +0000

Here's how to adjust the number of status updates on 3.2.x without any core file edits. This is helpful for those using a hosted community as they will not be able to perform an edit to an otherwise encoded file.

Connect via FTP. Open /conf_global.php. Just above the closing ?> tag, on its own line add:

$INFO['status_sidebar_show_x']            =    '10';

Save the change, adjust the 10 if you prefer a different number. The default if that line is missing is 5.

Note: Ensure that conf_global.php is not writeable after you've re-uploaded it, typically you would CHMOD it to 644 or 444 if possible. Never leave it at 777.

Customize Like Button in 3.2.0

Mon, 25 Jul 2011 12:59:43 +0000

Maybe many communities need little customization of like button. With this tutoria you can customize colours and texts.

1)Image background erase: upload 2 file attached in your skin images folder

2)Color customization: Look&Feel - manage skin set & template - your skin - css -ipb_stayle.css and find:

	.ipsLikeButton.ipsLikeButton_enabled {
		background: #850600 url({style_images_url}/like_button.png ) no-repeat top left;
		border: 1px solid #850600;
	}

and change the 2 colors code 7B96BB with your preferred color

3)Text customization: Look&Feel - manage language - open your official lang - use search field to find "like_this" - and you can change the text now

Before:

After:

--------------------------------------

Below the 2 images attached

Autocheck 'leave a link' when moving a topic or topics

Sun, 24 Jul 2011 14:01:29 +0000

Here's a simple article on how to set "Leave a link to the new topic in the source forum?" for both individual and mass moving topics as by default they are both unchecked.

Two small skin edits are needed, the template names are very similar so be careful to not mix them up. , the first one is MoveTopicForm the second is MoveTopicsForm

ACP > Look / Feel > Skin Manager > (choose skin) > Manage Templates / CSS > Moderation > MoveTopicForm

Find...

			
				
				{$this->lang->words['leave_link']}

Change to...

			
				
				{$this->lang->words['leave_link']}

Save the change.

ACP > ACP > Look / Feel > Skin Manager > (choose skin) > Manage Templates / CSS > Moderation > MoveTopicsForm

Find...

			
				
				{$this->lang->words['leave_link']}

Change to...

			
				
				{$this->lang->words['leave_link']}

Again, save the change.

That's it, it should be done. Here's two quick pics although its quite obvious what its done:

Autocheck use first tag as prefix

Sun, 24 Jul 2011 13:36:18 +0000

Here's a quick and very simple article on how to make the 'Use first tag as prefix' box checked by default to hopefully increase your members use of tags.

Members can uncheck it if they wish, I did consider hiding it but that negates it being there as this way they can opt out of using it if they still wish to use tags, it just serves as a helpful feature.

A tiny skin edit is needed.

ACP > Look / Feel > Skin Manager > (choose skin) > Manage Templates / CSS > Other Global Templates > TagTextEntryBox

Find...


	  checked='checked' /> {$this->lang->words['firsttagprefix']}

Replace with...


	  checked='checked' /> {$this->lang->words['firsttagprefix']}

Save the change. Repeat for other skins if required.

Here's a quick pic anyway: