NewsBot

<span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'>This hook displays an inline form for <a href='http://www.directupload.net' class='bbc_url' title='External link' rel='nofollow external'>directupload.net</a> </span></span></span><span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'>in the post form. When the 'Add Image' button is pressed the selected file will be uploaded and the </span></span></span><span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'>directupload.net page</span></span></span><span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'> is opened in a new window to show it.</span></span></span><br /><span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'> </span></span></span><br /><span style='color: rgb(40,40,40)'><span style='font-family: helvetica'><span style='font-size: 12px;'>You are able to exclude forums, in which the upload form should not be displayed.</span></span></span> Pobierz plik

Development is much more than just opening a text editor and writing some code. This is how most developers start, of course, and may be what an individual developer's day to day duties entail at a large corporation, however when viewing the "big picture" there are many other decisions that must be made in the course of building a software package for release that clients often don't realize were even considered. We thought you might be interested in hearing about some of those decisions that were made regarding 4.0, prior to ever writing a single line of code. Minimum Supported Versions One decision that has to be made relatively early in the development process is what dependencies will the software require. For software developed in PHP, this typically means what version of PHP will be the minimum, and (often) what will be the minimum required version of MySQL. PHP 5.3.0 was released in June of 2009, and includes functionality that we intend to utilize within the 4.0 Suite. Subsequently, this was an easy decision to make. We were leaning towards requiring MySQL 5.5, which was also released in 2009. We feel that 3 years is long enough on the web to incorporate updated software within most hosting environments. Upon investigating the functionality we intend to utilize in MySQL, however, we have determined that MySQL 5.0.3 and above includes everything we need, so MySQL 5.0.3 will be our minimum required version. Profiling and Benchmarking If you are a PHP developer and have ever attempted to profile your code, you probably realize it can be challenging. Many IDEs support some level of profiling built in, however it is almost always manually invoked. xdebug is a powerful tool for profiling, but again it requires you to enable profiling, run a request, and then view the results. In a live environment this is nearly impossible as profiling adds a lot of overhead to page loads and creates hundreds of profiling files quickly. Our goal is to be able to profile changes as they are committed, right away. We have decided to install Zend Server to the server that will host our staging environment for 4.0, which supports automatic rule-based built in profiling. This will allow us to easily profile requests automatically, even those that we may not "know" how to trigger manually (e.g. a specific task in a specific circumstance takes a long time to execute). Improving automatic deployments While automatically building and deploying the software to our staging environment itself is not a challenge per-se, a lot of times changes occur that require some sort of manual intervention to enact. We may have exported updated skin templates, language files, or there may be SQL queries that need to be run. We are developing an automatic deployment routine that can handle all of this easily and programatically, ensuring our staging environment is truly always up to date with the latest changes. Website and forum organization Not directly related to 4.0, another area we had to consider was our organization on the website and on our community here. This extend to all areas of the community, from the organization of our feedback and support forums, to our marketplace categorization, to our bug tracker categorization. The approach with 4.0 will be that we have one suite with modular applications that can be enabled. We need to market the software this way, and we need to ensure that the logical work flow for our clients reflects how our suite is designed. You will be seeing changes to categorization throughout our sites based on 4.0 in due course as a result. Loose ends And beyond all of the stuff directly related to 4.0, we felt it prudent to tackle a lot of loose ends before we jumped into a major overhaul of our entire software line up. There were a lot of smaller tasks that have been pushed off for a while but which we've finally sorted through which we feel will afford us less distractions as we work on the next release. Most of these tasks were minor, but not unimportant. Examples include: Moving our documentation to the main website Improving minor areas of IP.Downloads and IP.Nexus to allow clients to better help themselves, or to allow a smoother work flow within the administration areas our employees utilize every day Scripts on our end that allow us to better manage certain services Cleaning up old content in our installation, such as removing unused IP.Content blocks and deleting left over files on our server None of this directly affects 4.0, however the less distracted we get with minor tasks during 4.0 development, the better we can focus and deliver the product in a timely manner and with less chance of distraction-related bugs. Of course hundreds of other decisions have gone into 4.0 as well, some of which we will talk about in future blog entries. We thought you might be interested in hearing about some of the smaller things us developers do here at IPS, however, besides developing great software products to power your communities! Wyświetl pełny artykuł

<strong class='bbc'><span style='font-size: 18px;'>Introduction</span></strong><br />The Kerberos Loginauth method allows you to authenticate your users against an external Kerberos server (such as Active Directory) in cases where LDAP may not be available.<br /> <br /><strong class='bbc'><span style='font-size: 18px;'>Requirements</span></strong><br />A working kerberos installation must be present on your server. The Ubuntu package name for this is krb5-user. You must also install the development libraries in order to compile the krb5 extension for PHP. You can verify your kerberos installation by running the "kinit" command.<br /> <br />This loginauth module requires the PHP krb5 extension, which may be downloaded at <a href='http://svn.php.net/repository/pecl/krb5/trunk/.' class='bbc_url' title='External link' rel='nofollow external'>http://svn.php.net/r...cl/krb5/trunk/.</a> To download and install the extension on Linux, follow these steps:<ul class='bbcol decimal'><li>run svn checkout <a href='http://svn.php.net/repository/pecl/krb5/trunk/' class='bbc_url' title='External link' rel='nofollow external'>http://svn.php.net/r...ecl/krb5/trunk/</a></li><li>change directory to where the files downloaded</li><li>run phpize</li><li>run ./configure</li><li>run make && make install</li></ul><strong class='bbc'><span style='font-size: 18px;'>Installation/Uninstallation</span></strong><br />To install, extract the .zip file into your IPB install, the module's directory structure is already present inside of the zip file so it should be placed in the correct location automatically. To verify this, check that you see a directory named 'krb5' in your admin/sources/loginauth directory.<br /> <br />Once present, navigate to your Admin CP -> System -> Tools & Settings -> Log In Management and click the Install icon next to "Kerberos."<br /> <br />To uninstall, navigate to your Admin CP -> System -> Tools & Settings -> Log In Management and select Uninstall from the dropdown next to "Kerberos."<br /> <br /><strong class='bbc'><span style='font-size: 18px;'>Configuration</span></strong><br />Configuring Kerberos authentication is done via two separate methods, the configuration pane in the Admin CP and by creating a krb5.conf file. Regardless of configuration, local database authentication to the Admin CP is always allowed to ensure that in the event of misconfiguration, an admin can log in and fix the issues.<br /> <br /><strong class='bbc'><span style='font-size: 14px;'>Admin CP</span></strong><br />There are many configuration options available in the Admin CP. You can access these by clicking the gear icon next to the "Kerberos" method in Log In Management.<ul class='bbc'><li><em class='bbc'>Kerberos Default Authentication Realm</em> - This is the realm (aka domain) that you are authenticating against if one is not specified by the user when logging in. This usually must be ALL UPPERCASE in order for Kerberos to recognize it. This configuration option is REQUIRED and must be specified.</li><li><em class='bbc'>User Can Specify Alternative Realms</em> - If "Yes" user may log into a realm other than the default realm above by passing username@REALM as their username. These realms still need to be configured in the krb5.conf file. If "No", the default realm specified above is automatically appended to the username and any realm the user specifies is stipped out.</li><li><em class='bbc'>Use Alternative Configuration File</em> - If "Yes" the alternative configuration file below will be used to get kdc and realm information, otherwise the system default (usually /etc/krb5.conf) will be used. Make sure to specify a full path to the file, as if the file does not exist or is not readable, all logins will fail.</li><li><em class='bbc'>Alternative Configuration File</em> - Specifies the path to the alternative configuration file. You may wish to copy your system's krb5.conf and modify it from there. This should be a full path to the file and the file must be readable. If this is specified and "Use Alternative Configuration File" is "Yes", the default configuration file will be ignored and this used in its place.</li><li><em class='bbc'>Require Local User</em> - Requires that a local user with the same username already exist before allowing Kerberos logins. This is useful in scenarios where you only wish for certain people to be able to log in (on a whitelist basis). If this is "Yes", and admin must first create a local user account for each user before they may log in with their Kerberos credentials.</li><li><em class='bbc'>Email Address Pattern</em> - What to set as the e-mail address when creating a new local account. Leave this blank to force the user to type in an email address when they first log in. The following variables are replaced in the pattern:<br /><ul class='bbc'><li>{USERNAME} - Username</li><li>{REALM} - Authentication realm (lowercase)</li></ul>For example, if this was "{USERNAME}@mail.{REALM}" and a user logged in as [email protected], this would set their email address when creating their local account to "[email protected]". This setting only applies when creating a NEW local user account, it will not adjust the email addresses of an existing account.</li><li><em class='bbc'>Update Local Password</em> - Upon successful Kerberos login, should we update the user's local password to match? If set to "Yes", the password stored in the local database is updated to match the password used to log into Kerberos. If no, the password in the local database is not modified.</li></ul><strong class='bbc'><span style='font-size: 14px;'>krb5.conf</span></strong><br />You may either use the system's krb5.conf file (usually located at /etc/krb5.conf) or specify your own via the configuration in the Admin CP. The krb5.conf file must specify what realms you are allowing users to log in with as well as the Key Distribution Centers (KDCs) for those realms. The syntax and configuration of krb5.conf is beyond the scope of this readme and many good guides exist on the internet.<br /> <br /><strong class='bbc'><span style='font-size: 18px;'>Bugs/Feedback</span></strong><br />Please report all bugs and feedback to the thread in the IPS Marketplace. Pobierz plik

This hook allows users to receive a notification when they are mentioned in a post. Features include:<ul class='bbc'><li>Ability to change mention character (default is '@')</li><li>Ability to display @mention link in userinfopane of posts</li><li>Ability to bypass user configuration so notifications are always sent</li></ul><span style='color: #ff0000'><span style='font-size: 14px;'><strong class='bbc'>By purchasing this hook you agree to the following terms and conditions</strong></span></span><ul class='bbcol decimal'><li><strong class='bbc'>Licensing</strong> - This hook may not be redistributed for any purpose nor may it be used on multiple sites. If you would like to use this hook on multiple sites then you must purchase multiple copies.</li><li><strong class='bbc'>Support</strong> - While every attempt is made to ensure compatibility with multiple versions of IPS software support is only provided for the listed supported version of IPS software. As the software is updated the supported version is subject to change and previously supported software may be dropped. Additionally, only the default skin provided by IPS is supported. Support for custom skins or other versions of the software may be provided for a small fee. If you are having problems with the hook then you must be willing to provide FTP and ACP access so that the hook author can investigate the problem.</li><li><strong class='bbc'>English Only</strong> - This hook was created with the intention of only working in English. Other languages such as Arabic and Turkish appear to work as well, but only English is officially supported. If you would like to test support for your language please make a request in the support topic.</li><li><strong class='bbc'>Stupid Questions</strong> - You may not ask how to install this hook. The installation instructions are provided in the .zip file. Additionally, you may not ask if this hook is compatible with a certain version of the software. The supported version is listed on the download page.</li><li><strong class='bbc'>Modifications</strong> - You are permitted to modify the code, however, modifications will not be supported. </li><li><strong class='bbc'>Harassment</strong> - You may not send private messages to the author of this hook or attempt to request support for this hook of the hook author outside of the IPS support topic.</li><li>If you fail to abide by any of the above requirements then support for this hook will no longer be provided to you.</li></ul> Pobierz plik

This modification will allow you to integrate <a href='http://mailchimp.com/' class='bbc_url' title='External link' rel='nofollow external'>Mailchimp</a> to IPB board. <br /> <br />With defining Mailchimp API you will be presented with your existing mailing lists on Mailchimp account. You can choose which mailing lists you want to tie to your system. <br /> <br />System supports double verification.<br /> <br />Users will have ability to sign up Mailing list through Registration or their User Control Panel.<br /> <br /> Pobierz plik

The Language Variables hook allows you to define language strings with variable replacements, as well as various text transformations. The hook exposes a PHP API to replace variables in a language string as well as a new parse block to be used within skin templates to do the same. This has an advantage over the "traditional" way of variable replacement via sprintf() due to allowing skin templates to define the replacements in addition to PHP files, as well as the function support.<br /> <br />For more information, including installation and usage guides, please see the readme_langvars.txt included with this submission. Pobierz plik

In 4.0, we have made changes to the database class to make use of prepared statements. For insert and update queries, the syntax is the same as it always has been: However, where previously the database class would try to work out the type of variable passed to it - it now binds these to a prepared statement. The real usefulness of this change though, is apparent when you need to use a where clause. Where previously you'd have to do something like this: You can now do: We calculate the datatype based on the variable datatype, so previously where you had to do things like $this->DB->setDataType( 'foo', 'string' ) when you wanted to store a value like '01' - ew) - you can now just cast the variable to whatever datatype you like. For example, if you wanted to ensure that the variable was cast as a string to avoid issues where a user name of '007' was detected as an integer and converted to '7' then you'd use:

This hook will give administrators and moderators the ability to put topics under special surveillance, by adding a badge (risk of closure) and message in specific places to users get advised that won't be tolerated flaming/discussions on those topics.<br />Administrators and moderators will have access to a new area on My Settings (User Control Panel) to get a list of all topics under special surveillance.<br /> <br /><strong class='bbc'>Badge <span style='color: #ff0000'>RISK OF CLOSURE</span> will appear on</strong>:<br /> <ul class='bbc'><li>Forum view</li><li>Topic view</li><li>Search results (View New Content, User Content and Regular Search)</li></ul> <br /><strong class='bbc'>Message will appear</strong>:<br /> <ul class='bbc'><li>Above fast reply on every topic that is under special surveillance</li><li>Post screen (full form) of topics that is under special surveillance</li></ul> <br /><strong class='bbc'>Settings</strong>:<br /> <ul class='bbc'><li>Forums where the hook will work</li></ul> <br /><strong class='bbc'>Compatibility</strong>:<br /> <ul class='bbc'><li>IP.Board 3.4.X</li><li>IP.Board 3.3.X</li></ul> Pobierz plik

We have built public beta releases of our entire product line up for testing. Please be aware that beta releases are not supported by IPS technical support. We do not recommend running them on a live site, you may be unable to upgrade from a beta release to the final version, and our only course of support is to recommend you restore a backup of your site if you face any issues. We appreciate clients who wish to participate in beta testing programs. We would recommend cloning your live site, or installing these betas to a new test environment, in order to test the bug fixes and functionality improvements. Please report bugs in the bug tracker. As of the time of this post, our company forums are running all of these latest versions. IP.Board 3.4.3 Bug fixes IP.Blog 2.6.2 Bug fixes IP.Calendar 3.3.2 Bug fixes IP.Chat 1.4.3 Bug fixes IP.Content 2.3.5 Bug fixes IP.Downloads 2.5.3 Bug fixes Multiple featured files now supported Ability for clients to manage renewals for purchased files now supported IP.Gallery 5.0.4 Bug fixes Ability to create Gallery IP.Content feeds filtering on "featured" status now supported IP.Nexus 1.5.7 Bug fixes Integration with the bulk mailer supported Ability to leave a customer note when voiding account added You can download beta releases for which your license gives you access to at our QA page. Thanks in advance to all who decide to test! Wyświetl pełny artykuł

This is just a quick update to let everyone know of a small enhancement you can expect to see in the next IP.Gallery release. We recently noticed that you could not create IP.Content feed blocks to pull featured images from IP.Gallery. We felt that this was a small and easily correctable oversight, so we added a filter option when creating IP.Gallery feed blocks in IP.Content to allow you to choose whether to pull only featured images or not. You can expect to see this new option beginning with the IP.Gallery 5.0.4 release. Adding filters to IP.Content feed blocks is a generally easy process, depending upon what you are trying to filter by. Naturally, some types of filters can make the block much more complex, but with the example above of filtering by retrieving featured images, we needed only 2 language strings and 10 distinct lines of code. What types of block filters have you always felt would be easy but useful additions? Wyświetl pełny artykuł

<span style='color: #ff8c00'><strong class='bbc'>Orange </strong></span>| <span style='color: #ff0000'><strong class='bbc'>Red </strong></span>| <span style='color: #008080'><strong class='bbc'>Cyan</strong> </span>Buttons in Post Editor<br /> <br />Codes:<ul class='bbcol decimal'><li>[o] Orange bar [/c]</li><li>[r] Red bar [/r]</li><li>[c] Cyan bar [/c]</li></ul> <br />Useful to Highlight Headings in Posts.<br /> <br /><em class='bbc'><span style='color: #ff0000'><strong class='bbc'>Instruction:</strong></span></em><br /> <br /><strong class='bbc'>Read <span class='bbc_underline'>"Read Me.txt"</span> File from .zip</strong> Pobierz plik

A while back, we casually mentioned in a blog entry that 4.0 would be next major version after 3.4. Development of 4.0 is underway and we're going to be using this new blog to talk about development as we go. As Brandon mentioned a couple of days ago - the format of these entries is going to be developer-specific. If what we're saying doesn't make much sense right now, we will still be putting announcements up in our main blog when they're finished and ready for everyone to see. Because of that, it's also worth bearing in mind that everything is subject to change. I'm going to be posting code samples, screenshots and so forth - but everything in this blog is a work in progress - not the final product - and that will probably show. With that out the way - let's talk about 4.0! The file structure Currently, applications are mostly self contained in their folders (which is either /admin/applications, /admin/applications_addon/ips or /admin/applications_addon/other) however, other files are dotted around in /interface, /public, etc. In 4.0, applications will be completely self-contained within a single /applications directory. An application directory will look something like this: extensions dev css html img js lang interface modules admin front (it's "front" rather than "public" now) setup sources tasks xml You will notice the inclusion of a /dev folder. This will not actually be shipped in production, but rather replaces /cache/lang_cache/master_lang and so forth in the 3.x line. Outside of the applications directory, there will be a "system" directory, which contains core framework classes. Namespaces and autoloading In 4.0, we'll be making use of PHP namespaces and using an autoloader. The best way to demonstrate how this works is with a few examples: classDb (/ips_kernel/classDb.php) is now IPSDb and located in /system/Db/Db.php output (/admin/sources/classes/output/publicOutput.php) is now IPSOutput and located in /system/Output/Output.php class_forums (/admin/applications/forums/sources/classes/forums/class_forums.php) is now IPSforumsForum and located in /applications/forums/sources/Forum/Forum.php IPSDispatcherFront and IPSDispatcherAdmin are two new classes (with similar functionality to ipsController in 3.x) and both extend IPSDispatcherDispatcher - all 3 are located in /system/Dispatcher/ in individual files. Better framework design Where appropriate, classes are being refactored to make better use of appropriate design patterns. One lovely side-effect of this is ipsRegistry no longer exists. Instead of, for example ipsRegistry::DB() you now use IPSDb::i() - the Db class uses a multiton design pattern (I didn't pass any arguments in that example, which doing will cause the Db class to load conf_global.php and create the default database connection, but I could have passed it a key) - the i method in this case will create the database connection if it doesn't already exist. To give another example - IPSMember (the new IPSMember) uses an Active Record pattern. So there's no more of this: IPSMember::isInGroup( 1, 4 ); It's now, the much more logical: IPSMember::load( 1 )->isInGroup( 4 ); Monkey patching hooks One of the great things about the IPS Community Suite is hooks - you can easily create a class and instruct the framework to use that instead of a core class. Now, I don't know about you, but I really, really, really hate having to do this: $class = IPSLib::loadLibrary( '/path/to/file', 'myClass' ); $object = new $class; Especially if what you want to call is a static method, in which case it can't be done. You want to of course, just be able to do: $object = new myClass; or: myClass::myStaticMethod(); There is a concept in software engineering to do this sort of thing, called monkey patching, and by clever use of the autoloader, we've managed to make this work. loadLibary and loadActionOverloader are no more. These points are of course, just the beginning of 4.0. Stay tuned for more Wyświetl pełny artykuł

Hello my friends.<br /> <br />here is a customized IPB Skin for (all) <strong class='bbc'>Mobile Devices </strong>.<br /> <br /><em class='bbc'><span style='color: #008000'><strong class='bbc'>Features: </strong></span></em><ul class='bbcol decimal'><li>Shoutbox</li><li>Post Like / Unlike Feature</li><li>Who Like this post</li><li>Board Stats on index page</li><li>Search Module</li><li>Notification (Counts) and Page with moderation</li><li>Private Message (Counts) and Messenger Page with moderation</li><li>Profile Page</li><li>Can use WYSIWYG Editor to post from PC</li><li>Moderation Tools and Buttons</li><li>Login with Facebook and Hotmail</li><li>Compressed Post Images to Fit in Mobile Screen sizes</li><li>Subforum Links</li><li>Formatted Usernames in Post View</li><li>Very Fast Mobile Theme</li></ul><span style='color: #ff0000'><em class='bbc'><strong class='bbc'>How to Install :</strong></em></span><br /> <br />Read <strong class='bbc'>"Read Me.txt"</strong> from package Pobierz plik

This application will enable you to set a maximum number of threads for your groups for a certain time frame on a forum per forum basis.<br /><br />Installation and Configuration:<br /><br />To install this application, upload the admin folder inside the Upload folder to the root of your forum folder. Then go to your Admin Panel->Application&Modules->Manage Applications & Modules and on the right side where it says: Applications Not Installed you will see a new application added called: Maximum Threads Limit. Click on the install button.<br /><br />To set the time frame threads limit, go to the Forums tab then from the drop down list choose Manage Forums. Then choose the forum and/or the forums that you want to enforce the threads limit for a certain time frame, click the edit button and you will see an extra tab added there called: Maximum Threads Limit.<br />Click it and there you can configure its settings to your likings/needs.<br /><br />1) Set the maximum number of threads for that particular forum.<br /><br />2) Choose the time frame for the threads limit.<br /><br />3) Choose the group/s that you want to enforce the time frame threads limit.<br /><br />4) And as last but not least you can set your own custom error message as well that will appear when the time frame thread limit is exceeded.<br /><br />Several screenshots of the application are attached so it will give you a more detailed idea on how it looks like when being used. Pobierz plik

This is a simple hook that will add a new notification option for your users when their posts will be edited.<br /><br />After you install the hook, the notification option can be enabled at Profile->My Settings->Notification Options->Forums->Notify me when my posts are edited and save the changes. Now anytime your post is edited you will receive a new notification letting you know about that fact showing who edited your post and the link to the post that was edited.<br /><br />Several screenshots of the hook are attached so it will give you a more detailed idea on how it looks like when being used. Pobierz plik

While we <a href='http://community.invisionpower.com/blog/1174/entry-7634-license-changes-ipboard-34-and-the-future/' class='bbc_url' title=''>introduced some of our basic plans for 4.0</a> many months ago, we wanted to touch base again on some of these plans and expand upon some of our motivations behind decisions we have or will make for our upcoming 4.0 software release.<br /> <br />Before we get too far, let me just state now that there is no expected (or even estimated) release date for 4.0 yet. While we always have internal guidelines, timeframes and milestones, we do not communicate these publicly until we are absolutely sure they are as accurate as possible. The 4.0 Suite will be a major overhaul, effectively a rewrite of most areas from the ground up, and there are many factors that can affect delivering within expected due dates.<br /> <br />You may also have noticed the title of this blog entry uses a term for the suite you may not have seen used previously. We have decided to name the 4.0 Suite (which we will often refer to as "4.0 Suite" or "Social Suite", informally), officially as the IPS Social Suite. We feel that as we expand our line up and remove community-related dependencies, it is important that our main product release reflect the fact that our software can power more than just traditional communities.<br /> <br />Formalities out of the way now, here are a few of our driving motivations behind 4.0...<br /> <br /><span style='font-size: 18px;'><strong class='bbc'>Modernize the interface</strong></span><br />The skin delivered for 3.0 and again for 3.2 was great, but several years have since passed. It is time we modernize the user interface in our software lineup once again. Features have been added, trends on the web have shifted, and technologies have advanced. Some specific points you may be interested to know:<ul class='bbc'><li>All areas of the suite will support the mobile interface.</li><li>We are heavily investigating using a "response design" for 4.0.</li><li>We will be switching to jQuery</li><li>We will be embracing HTML 5 fully</li></ul> <br /><span style='font-size: 18px;'><strong class='bbc'>Modernize the underlying codebase</strong></span><br />While 4.0 will not technically be a "complete rewrite", most of the underlying codebase will be rewritten in some manner, and all of the code will at least be updated to work within the new framework we are developing. There is a lot to go over for those of you who may be interested in the developer side of things, and I'll point you to the right place later in this entry, but as a general outline here are some things you can expect to see:<ul class='bbc'><li>PHP 5.3 will be the minimum supported version of PHP</li><li>MySQL 5.0.3 will be the minimum supported version of MySQL</li><li>IP.Board will fully utilize namespaces in PHP</li><li>The entire directory structure, class naming structure and more will be completely overhauled</li><li>Applications will truly be self-contained within their own folders (currently javascript, skin and language files, for instance, are scattered throughout miscellaneous directories)</li><li>The entire code base will be modernized. More use of formal design patterns will be employed, where appropriate. Dumping ground classes (such as IPSLib) will be avoided at all costs. More consistency between how applications implement functionality will be seen. Naming conventions will be more consistent.</li><li>The way hooks work will be completely rewritten, making things simpler for us and for developers, and making hook usage behind the scenes more reliable (no more loadLibrary calls - everything is handled automatically by the framework instead).</li></ul> <br /><span style='font-size: 18px;'><strong class='bbc'>Make things more consistent</strong></span><br />We are also working towards making all of our applications more consistent. The approach to this actually has much more to do with planning and how we approach new functionality than it does any specific technical aspect of software development. In a nutshell, we will have one "suite" release moving forward starting at 4.0. Every application will be on the same versioning system and share the same version number, and every release will include every application (although you will only have access to the applications you have purchased, of course). What we will do as we implement new features is implement new functionality suite-wide from the start. If we were to add a new feature to 4.0, we would not add the functionality to the forums and then roll this change out to other applications as they see updates. Instead, we will be implementing changes suite-wide from the start, which has several benefits:<ul class='bbc'><li>From a user standpoint, the software will be more consistent. You won't have situations where a feature is available in Application X but not in Application Y.</li><li>From a technological standpoint, we will be forced to implement functionality in an optimal manner where it can be utilized by all areas of the suite. There will be less application-dependencies for features that are intended to be suite-wide. There will be much, much less duplicated code as features will be designed from the start to work in multiple areas.</li><li>Point #2 above will also benefit modders - APIs will be much more robust, yet more generic and reusable, for features implemented suite-wide rather than features implemented for one application and then shared across others.</li></ul> <br />Beyond changing our approach to functional changes in the software itself, we will also be focusing on consistency while redesigning the interface, and throughout every facet of development of 4.0.<br /> <br /> <br /><span style='font-size: 18px;'><strong class='bbc'>Want to hear more specifics?</strong></span><br />We have <a href='http://community.invisionpower.com/blog/1174/entry-8637-ips-development-channel-blog/' class='bbc_url' title=''>recently launched our new development blog</a> where we will routinely be posting about the nitty-gritty of our day to day development duties here at IPS. While this blog is not at all intended to be specific to the development of 4.0, you will find us posting about upcoming changes and decisions made in 4.0 quite regularly. We welcome you to follow <a href='http://community.invisionpower.com/blog/4445-the-development-channel/' class='bbc_url' title=''>The Development Channel</a> blog if you are interested in reading about these changes. If not, don't worry - any major announcements will be blogged about here in our company blog as well in due course.<br /> <br />If you aren't sure, just to be clear....development of 4.0 is definitely underway. A lot of planning and discussion took place prior to ever writing a single line of code for 4.0, however we are definitely working on 4.0 now and you will likely see blog entries about upcoming changes before long. Stay tuned! Zobacz cały wpis

While we <a href='http://community.invisionpower.com/blog/1174/entry-7634-license-changes-ipboard-34-and-the-future/' class='bbc_url' title=''>introduced some of our basic plans for 4.0</a> many months ago, we wanted to touch base again on some of these plans and expand upon some of our motivations behind decisions we have or will make for our upcoming 4.0 software release.<br /> <br />Before we get too far, let me just state now that there is no expected (or even estimated) release date for 4.0 yet. While we always have internal guidelines, timeframes and milestones, we do not communicate these publicly until we are absolutely sure they are as accurate as possible. The 4.0 Suite will be a major overhaul, effectively a rewrite of most areas from the ground up, and there are many factors that can affect delivering within expected due dates.<br /> <br />You may also have noticed the title of this blog entry uses a term for the suite you may not have seen used previously. We have decided to name the 4.0 Suite (which we will often refer to as "4.0 Suite" or "Social Suite", informally), officially as the IPS Social Suite. We feel that as we expand our line up and remove community-related dependencies, it is important that our main product release reflect the fact that our software can power more than just traditional communities.<br /> <br />Formalities out of the way now, here are a few of our driving motivations behind 4.0...<br /> <br /><span style='font-size: 18px;'><strong class='bbc'>Modernize the interface</strong></span><br />The skin delivered for 3.0 and again for 3.2 was great, but several years have since passed. It is time we modernize the user interface in our software lineup once again. Features have been added, trends on the web have shifted, and technologies have advanced. Some specific points you may be interested to know:<ul class='bbc'><li>All areas of the suite will support the mobile interface.</li><li>We are heavily investigating using a "response design" for 4.0.</li><li>We will be switching to jQuery</li><li>We will be embracing HTML 5 fully</li></ul> <br /><span style='font-size: 18px;'><strong class='bbc'>Modernize the underlying codebase</strong></span><br />While 4.0 will not technically be a "complete rewrite", most of the underlying codebase will be rewritten in some manner, and all of the code will at least be updated to work within the new framework we are developing. There is a lot to go over for those of you who may be interested in the developer side of things, and I'll point you to the right place later in this entry, but as a general outline here are some things you can expect to see:<ul class='bbc'><li>PHP 5.3 will be the minimum supported version of PHP</li><li>MySQL 5.0.3 will be the minimum supported version of MySQL</li><li>IP.Board will fully utilize namespaces in PHP</li><li>The entire directory structure, class naming structure and more will be completely overhauled</li><li>Applications will truly be self-contained within their own folders (currently javascript, skin and language files, for instance, are scattered throughout miscellaneous directories)</li><li>The entire code base will be modernized. More use of formal design patterns will be employed, where appropriate. Dumping ground classes (such as IPSLib) will be avoided at all costs. More consistency between how applications implement functionality will be seen. Naming conventions will be more consistent.</li><li>The way hooks work will be completely rewritten, making things simpler for us and for developers, and making hook usage behind the scenes more reliable (no more loadLibrary calls - everything is handled automatically by the framework instead).</li></ul> <br /><span style='font-size: 18px;'><strong class='bbc'>Make things more consistent</strong></span><br />We are also working towards making all of our applications more consistent. The approach to this actually has much more to do with planning and how we approach new functionality than it does any specific technical aspect of software development. In a nutshell, we will have one "suite" release moving forward starting at 4.0. Every application will be on the same versioning system and share the same version number, and every release will include every application (although you will only have access to the applications you have purchased, of course). What we will do as we implement new features is implement new functionality suite-wide from the start. If we were to add a new feature to 4.0, we would not add the functionality to the forums and then roll this change out to other applications as they see updates. Instead, we will be implementing changes suite-wide from the start, which has several benefits:<ul class='bbc'><li>From a user standpoint, the software will be more consistent. You won't have situations where a feature is available in Application X but not in Application Y.</li><li>From a technological standpoint, we will be forced to implement functionality in an optimal manner where it can be utilized by all areas of the suite. There will be less application-dependencies for features that are intended to be suite-wide. There will be much, much less duplicated code as features will be designed from the start to work in multiple areas.</li><li>Point #2 above will also benefit modders - APIs will be much more robust, yet more generic and reusable, for features implemented suite-wide rather than features implemented for one application and then shared across others.</li></ul> <br />Beyond changing our approach to functional changes in the software itself, we will also be focusing on consistency while redesigning the interface, and throughout every facet of development of 4.0.<br /> <br /> <br /><span style='font-size: 18px;'><strong class='bbc'>Want to hear more specifics?</strong></span><br />We have <a href='http://community.invisionpower.com/blog/1174/entry-8637-ips-development-channel-blog/' class='bbc_url' title=''>recently launched our new development blog</a> where we will routinely be posting about the nitty-gritty of our day to day development duties here at IPS. While this blog is not at all intended to be specific to the development of 4.0, you will find us posting about upcoming changes and decisions made in 4.0 quite regularly. We welcome you to follow <a href='http://community.invisionpower.com/blog/4445-the-development-channel/' class='bbc_url' title=''>The Development Channel</a> blog if you are interested in reading about these changes. If not, don't worry - any major announcements will be blogged about here in our company blog as well in due course.<br /> <br />If you aren't sure, just to be clear....development of 4.0 is definitely underway. A lot of planning and discussion took place prior to ever writing a single line of code for 4.0, however we are definitely working on 4.0 now and you will likely see blog entries about upcoming changes before long. Stay tuned!<br /><br /><a href='http://community.invisionpower.com/blog/1174/entry-8650-ips-social-suite-40/' class='bbc_url' title=''>View the full article</a> Zobacz cały news

With this mod you can add a members memorial at the bottom of your board.<br /> <br /> Fetaures:<br /><br /> • enable/disable app<br /> • select groups that can view the memorial panel<br /> • add title on panel<br /> • control marquee speed<br /> • control marquee direction<br /> • control pause<br /> • add birth date , death date and photo<br /> • topic creation<br /> • and more.. Pobierz plik

This hook will display a list of popular topics in the sidebar based on the number of replies a topic has received in the past X days. Features include:<ul class='bbc'><li>Changing the number of days to poll for replies</li><li>Toggling the reply counter</li><li>Displaying a compact view with only topic titles</li><li>Changing the number of topics to display</li><li>Choosing which forums are blocked from the list (permissions are respected)</li></ul> Pobierz plik

This hook will create a sidebar block to display recent topics from your board.<br /> <br /><strong class='bbc'>Settings</strong>:<br /> <ul class='bbc'><li>Number of topics to display</li><li>Show topic prefix</li><li>Show ANSWERED tag*</li><li>Show PINNED tag</li><li>Show POLL tag</li><li>Show topic STATE image</li><li>Groups that can view the sidebar block</li><li>EXCLUDE Forums</li></ul> <br /><strong class='bbc'>Compatibility</strong>:<br /> <ul class='bbc'><li>IP.Board 3.4.X</li><li>IP.Board 3.3.X</li></ul> <br /><strong class='bbc'>Notes</strong>:<ul class='bbc'><li>(*) ANSWERED tag isn't available for IP.Board 3.3</li><li>This is <strong class='bbc'>NOT </strong>the Recent Topics from IPS. You have to uninstall it or disabled it.</li></ul> Pobierz plik

5 Designs of Team rank icons for IPB forum.<br /><br />Please do not redistribute these without my permission.<br /><br />Usage:<br />Includes 5 different designed blanks to create your own your way and/or in your own language.<br />Also includes 5 example admin ranks, 5 example moderator ranks, and 5 example member ranks.<br /><br />Credit:<br />Created by CallieJo at IPB.<br /><br />Please do not ask for the psd. I am not providing it. Sorry. Pobierz plik

This hook will add a box with with the hottest/most active forums at your sidebar.<br /><br />Installation: Install the hook.xml file through Manage Hooks in your Admin Panel and then to configure it go to System Settings where you will see a new setting called NenaDice. Click on it and configure the hook to your needs.<br /><br />There you can enable/disable the hook, set the number of the hottest/most active forums that you would like to show at the sidebar, choose the group/s that you want to restrict from viewing the hottest forum box.<br /><br /><br />Also permissions will remain contact. Meaning the users will see only those forums that they have access to. Pobierz plik

Team rank icons for IPB forum.<br /><br />Please do not redistribute these without my permission.<br /><br />Usage:<br />Includes 5 different designed blanks to create your own your way and/or in your own language.<br />Also includes 5 example admin ranks, 5 example moderator ranks, and 5 example member ranks.<br /><br />Credit:<br />Created by CallieJo at IPB.<br /><br />Please do not ask for the psd. I am not providing it. Sorry. Pobierz plik

Please do not redistribute these without my permission.<br /><br />Usage:<br />Team rank icons for IPB forum.<br />Includes 10 different designed blanks to create your own your way and/or in your own language.<br />Also includes 10 example admin ranks and 10 example moderator ranks.<br /><br />Credit:<br />Created by CallieJo at IPB.<br /><br />Please do not ask for the psd. I am not providing it. Sorry. Pobierz plik

Please do not redistribute these without my permission.<br /><br />Usage:<br />Team rank icons for IPB forum.<br />Includes 10 different designed blanks to create your own your way and/or in your own language.<br />Also includes 10 example admin ranks and 10 example moderator ranks.<br /><br />Credit:<br />Created by CallieJo at IPB.<br /> <br />Please do not ask for the psd. I am not providing it. Sorry. Pobierz plik