Administrator

IPS is seeking a knowledgeable and experienced individual to join its support team in an advanced support capacity. Successful applicants will be responsible for answering general support tickets, including providing customers with information, troubleshooting issues not resolved as part of the general product support process and performing maintenance. You would be expected where appropriate to interact with other technicians and developers to resolve issues. Requirements: * Must be familiar with IPS applications. * Must have advanced knowledge of PHP and MySQL. * Must be able to effectively work remotely. * English must be your primary language and you must possess strong verbal and written communication skills. Preferable, but not required: * Knowledge of server administration and experience working for a web hosting company. * Knowledge of additional web technologies such as JavaScript, CSS, XML, etc. * Experience of working in customer support. * Experience working with the codebase or creating hooks/apps in the IPS Suite Working hours are flexible and pay will be based on knowledge and experience. Due to the nature of the position, we require all applicants to be physically located in the United States. No exceptions to United States residency requirements. Please contact hr@invisionpower.com for more information on this position. Please include your salary requirements, availability and an overview of your experience. We look forward to hearing from you! View the full article View the full article

cPanel has published security updates for all supported versions of cPanel & WHM. These updates contain fixes for a problem with the Roundcube webmail application. We recommend all customers update to the latest build of each version as soon as possible. The cPanel Security Team has assigned a rating of Important to the vulnerability. Information on security ratings is available at http://go.cpanel.net/securitylevels. A locally authenticated user could take advantage of the flaw to gain access to sensitive information belonging to other accounts on the system. This problem was reported to us in case 64407. If your deployed cPanel & WHM servers are configured to automatically update when new releases are available, then no action is required. Your systems will update automatically. If you have disabled automatic updates, then you are highly encouraged to update your cPanel & WHM installs at your earliest convenience. Releases The following versions of cPanel & WHM address all known vulnerabilities: * 11.36.0.20 * 11.34.1.13 * 11.32.6.4 The latest public releases of cPanel & WHM for all update tiers are published at http://httpupdate.cpanel.net. Click Here to view the PGP Signed Message. View the full article

Teh quick reply editor when open will check for new content every 10 seconds by default, to increase or decrease this time frame, edit the following. /public/ls/ips.textEditor.js Edit this line IPS_TEXTEDITOR_POLLING: 10000, /* 10 seconds */ Adjusting as follows to increase to 20 seconds as an example IPS_TEXTEDITOR_POLLING: 20000, /* 20 seconds */

Security Update: 21 March 2013 As part of our ongoing security auditing we have discovered a possible security issue. We are releasing a critical security update today to address this issue. Instructions We are providing a patch for IP.Board versions 3.4, 3.3, 3.2, and 3.1. Version 3.1 is end of life for support but we are still providing the patch for the convenience of clients who have not yet upgraded. If you are running a version less than 3.1 you should upgrade to get this and other security enhancements. Patching is very easy: Identify the version of IP.Board you are running. Download and unzip the appropriate patch file below that matches your version. Upload the contents of the extracted "upload" folder to your IP.Board home directory If you have renamed your admin directory, then copy the files manually to the appropriate admin folder. IP.Board 3.4.x ipb34_mar21.zip 2.58K 1111 downloads IP.Board 3.3.x ipb33_mar21.zip 2.58K 248 downloads IP.Board 3.2.x ipb32_mar21.zip 2.65K 109 downloads IP.Board 3.1.x ipb31_mar21.zip 2.68K 125 downloads Notes: When you apply the security update the bulletin in your AdminCP will still display. We keep the bulletin in place for at least a week after a security release. Our main software packages accessed via the client area have already been updated with this security update. If you are an IPS Hosting client your community has been automatically patched. View the full article

cPanel & WHM 11.32 reaches End Of Life August 20, 2013. That means there are only 5 months left in the life cycle. In accordance with our End of Life Policy cPanel & WHM 11.32 will continue functioning on servers after reaching End Of Life. No further updates, including security fixes, or installations will be provided for 11.32 after the End Of Life date. cPanel & WHM 11.32 is the last version to support the following: CentOS 4 RHEL 4 MySQL 4.0 MySQL 4.1 All customers currently using cPanel & WHM 11.32 are advised to begin planning the upgrade to cPanel & WHM 11.36 (EOL Date: March 2014). If you desire assistance with your migration plans, please contact our technical support team at https://tickets.cpanel.net/submit/. Our professional staff will help with recommendations, migration assistance and more. GPG signed version is available View the full article

Sometime over this weekend all servers will be updated to the latest available versions for all software. We will try to keep this to the late evenings as much as possible as this will require a reboot as well, this will result in a few minutes of downtime. However as you know we pride ourselves in ZERO downtime, however there are some items that do require a reboot for updating properly. If you have any concerns please let us know Thank you

http://youtu.be/2Kjh9lQXLWk

In the latest updates for 3.4.3 and all app, the gallery content slider was changed to resize the images to proper scale, this creates a smaller image on the slider that some may not like. To restore the older version look of the full image, do the following Place the attached slideshow.js file in the following location (adjust as needed for your proper path) /public_html/public/ipc_blocks/gallery_images_xxxxxxxx/slideshow.js Then go to other apps > content > blocks > recache template resources and you should be good! Before image After slideshow.js.zip

Invision Power Services, Inc. is pleased to announce the release of the following applications: IP.Board 3.4.3 IP.Blog 2.6.2 IP.Calendar 3.3.3 IP.Chat 1.4.3 IP.Content 2.3.5 IP.Downloads 2.5.3 IP.Gallery 5.0.4 IP.Nexus 1.5.7 IP.Board 3.4.3 IP.Board is a fully featured community platform including forums, members profiles, calendar, status system, integration, and much, much more. The release of IP.Board 3.4.3 is a maintenance release and includes bug fixes. IP.Blog 2.6.2 IP.Blog enables users to create and maintain their own individual or group blogs right from within your community, to share ideas & thoughts. The release of IP.Blog 2.6.2 is a maintenance release and includes bug fixes. IP.Calendar 3.3.3 IP.Calendar is an integrated calendar and event management for your IP.Board. The release of IP.Calendar 3.3.3 is a maintenance release and includes bug fixes. IP.Chat 1.4.3 IP.Chat is integrated chat software for your forum. Allow your members to chat to each other in real time. The release of IP.Chat 1.4.3 is a maintenance release and includes bug fixes. IP.Content 2.3.5 IP.Content is our community content management platform for IP.Board allowing you to create content for your site ranging from a simple portal to a full website with custom databases and more - the possibilities are endless! The release of IP.Content 2.3.5 is a maintenance release and includes bug fixes. IP.Downloads 2.5.3 IP.Downloads is an integrated download management for IP.Board allowing you and your members to upload files for sharing in an organized category listing with permissions, version control, and more. The release of IP.Downloads 2.5.3 is a maintenance release and includes Bug fixes Multiple featured files now supported Ability for clients to manage renewals for purchased files now supported IP.Gallery 5.0.4 IP.Gallery is a fully-featured photo and multimedia sharing app for the IPS Community Suite. Create albums, upload photos, discuss the hottest shots and much more. The release of IP.Gallery 5.0.4 is a maintenance release and includes Bug fixes Ability to create Gallery IP.Content feeds filtering on "featured" status now supported IP.Nexus 1.5.7 IP.Nexus is our fully featured commerce system to sell products, membership access, advertising, digital downloads, and more. Includes tools like a support desk to help manage your clients. The release of IP.Nexus 1.5.7 is a maintenance release and includes Bug fixes Integration with the bulk mailer supported Ability to leave a customer note when voiding account added How to Upgrade To upgrade simply log into your client area, click on "Purchases" from the menu and select the community you wish to upgrade and click "Upgrade Now". You can read more about upgrading in our documentation. View the full article

Depending on how a language pack author chooses to export a language pack, it can overwrite the default English (US) pack. This usually happens if you are provided with separate .xmls (such as members_language_pack.xml.gz) instead of a complete language.xml.gz file. It is preferable to use the latter 'complete' package where possible to avoid this. If your default English (US) has been overwritten and you wish to restore it, simply follow these steps. If you are not comfortable performing the following steps, please submit a ticket in the Client Centre for assistance. Taking a database backup is recommended before starting. Next, visit the SQL Toolbox: ACP > 'Support' tab > SQL Management > SQL Toolbox Run the following query: UPDATE core_sys_lang_words SET word_custom = '' WHERE lang_id = '1'; This assumes that the default language pack is still ID1, and has not been deleted. You may need to adjust the query slightly, adding your prefix if your board started on the 1.x or 2.x series. Assuming all went well, visit the Language Manager and choose to rebuild from xml. ACP > 'Look / Feel' tab > Manage Languages > and click the grey button on the right on the English (US) pack and choose 'Rebuild From XML' Wait for this to finish. It may take a minute or two. After this has completed, click the grey button again and choose 'Recache All...' View your board again. The default should of been restored. If it has not, you may wish to check the default xml's have not been replaced (although this is unlikely) , the locations are as follows: \admin\applications\core\xml\admin_core_language_pack.xml \admin\applications\core\xml\public_core_language_pack.xml \admin\applications\forums\xml\admin_forums_language_pack.xml \admin\applications\forums\xml\public_forums_language_pack.xml \admin\applications\members\xml\admin_members_language_pack.xml \admin\applications\members\xml\public_members_language_pack.xml The official applications are stored in the same fashion, but are located in: \admin\applications_addon\ips\ (application name) \xml\ Once these have been replaced with defaults from the .zip's as appropriate, follow the restoration steps again. If this does not work, please submit a ticket in the Client Centre for assistance.

IP.Board is able to use Gmail's SMTP service, if your server is configured properly. The first thing to check is whether your server is configured to allow it. Gmail SMTP uses a secured connection, so your PHP installation must have OpenSSL capabilities. To check this, go to ACP->Support->System Overview->PHP Info Scroll down the screen, you will see the installed modules, each under its own header, such as mbstring, mcrypt, mysql, mysqli and so on. You're looking for OpenSSL there in its own heading. Should look something like this.. openssl OpenSSL support enabled OpenSSL Version OpenSSL 0.9.8b 04 May 2006 Thought it will be formatted nicely in a table. Versions may be different, but so long as that is there, you will likely be able to use Gmail's SMTP. Go to ACP->System Settings->Email Setup, or in IP.Board 2.x, ACP->Tools and Settings->Email Setup. Set "Mail Delivery Method" to SMTP Set "Over-Ride SMTP Host" to tls://smtp.gmail.com Set "Over-Ride SMTP Port" to 465 Set "Add '<' and '>' to 'to' and 'from' addresses?" to Yes *Note that Gmail requires SMTP port 587 for TLS/STARTTLS and port 465 for SSL. More information is available in their documentation. Enter your Gmail username and password in the appropriate boxes. You should now be using Gmail SMTP to send mail on your forum. Run a test, such as registering a new account (assuming you have Email Validation) and verify that you receive the email.

Hi Loren, this is a little of a catch 22 here with the unarchiving and moving, you first need to unarchive all topics, then move them, however if you re-enable archiving at that point, those topics won't be re-archived. If a topic is unarchived, the system thinks it was done for a reason and won't archive that topic again. This isn't ideal in my opinion and leave room for improvement, if you wanted, after unarchiving, we could reset that flag, to clear it, then it would re-archive according to the rules you have set. Let me know if you have any questions, thank you

While we introduced some of our basic plans for 4.0 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. 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. 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. Formalities out of the way now, here are a few of our driving motivations behind 4.0... Modernize the interface 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: All areas of the suite will support the mobile interface. We are heavily investigating using a "response design" for 4.0. We will be switching to jQuery We will be embracing HTML 5 fully Modernize the underlying codebase 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: PHP 5.3 will be the minimum supported version of PHP MySQL 5.0.3 will be the minimum supported version of MySQL IP.Board will fully utilize namespaces in PHP The entire directory structure, class naming structure and more will be completely overhauled Applications will truly be self-contained within their own folders (currently javascript, skin and language files, for instance, are scattered throughout miscellaneous directories) 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. 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). Make things more consistent 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: 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. 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. 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. 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. Want to hear more specifics? We have recently launched our new development blog 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 The Development Channel 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. 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! View the full article View the full article

While we introduced some of our basic plans for 4.0 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. 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. 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. Formalities out of the way now, here are a few of our driving motivations behind 4.0... Modernize the interface 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: All areas of the suite will support the mobile interface. We are heavily investigating using a "response design" for 4.0. We will be switching to jQuery We will be embracing HTML 5 fully Modernize the underlying codebase 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: PHP 5.3 will be the minimum supported version of PHP MySQL 5.0.3 will be the minimum supported version of MySQL IP.Board will fully utilize namespaces in PHP The entire directory structure, class naming structure and more will be completely overhauled Applications will truly be self-contained within their own folders (currently javascript, skin and language files, for instance, are scattered throughout miscellaneous directories) 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. 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). Make things more consistent 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: 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. 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. 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. 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. Want to hear more specifics? We have recently launched our new development blog 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 The Development Channel 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. 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! View the full article

We have launched our new blog The Development Channel to allow our development staff to more frequently update our clients on everything that goes on behind the scenes. From the technical aspects, to fun insights, and new feature announcements you can follow The Development Channel to follow our software being made. View the full article View the full article

We have launched our new blog The Development Channel to allow our development staff to more frequently update our clients on everything that goes on behind the scenes. From the technical aspects, to fun insights, and new feature announcements you can follow The Development Channel to follow our software being made. View the full article

UPDATE forums SET can_view_others = 1;

Security Update: 7th February 2013 A cross-site-scripting (XSS) exploit has been discovered in IP.Gallery. We are releasing a security update for versions 4.2.x and 5.0.x today to patch this issue. Instructions: Patching is very easy; Identify the version of IP.Gallery you are running. Download and unzip the appropriate patch file below that matches your version. Upload the contents of the zip to your /public/js directory, overwriting the existing file. IP.Gallery 4.2.x ipg42_feb13.zip 831bytes 0 downloads IP.Gallery 5.0.x ipg5_feb13.zip 2.41K 2 downloads Notes: When you apply the security update the bulletin in your AdminCP will still display. We keep the bulletin in place for at least a week after a security release. Our main software packages accessed via the client area have already been updated with this security update. Our thanks to Mohamed Ramadan ( Attack-Secure.com / https://twitter.com/Attack_Secure ) for bringing this to our attention. View the full article

Place all images in desired directory, cd to directory. (make sure ImageMagick is installed) find . -name \*.jpg -exec convert -size '800x600' {} -resize '>800x600' {} \; This will allow the server to open the images at an 800x600 size, (saving memory and speeding up the conversion, and then resize to 800x600 (second -resize) So if you have thousands of images, some large and small, this will only re-size, according to your settings above.

Via htaccess <IfModule mod_headers.c> Header set X-UA-Compatible "IE=Edge,chrome=1" <FilesMatch "\.(js|css|gif|png|jpe?g|pdf|xml|oga|ogg|m4a|ogv|mp4|m4v|webm|svg|svgz|eot|ttf|otf|woff|ico|webp|appcache|manifest|htc|crx|oex|xpi|safariextz|vcf)$" > Header unset X-UA-Compatible </FilesMatch></IfModule>

Invision Power Services, Inc. is pleased to announce the release of IP.Board 3.4.2 The release of IP.Board 3.4.2 is a maintenance release. What's New in 3.4 Please read these blog entries for a full list and explanation of what's new in this release. IP.SEO Removed (we have removed IP.SEO and merged all its functionality right into IP.Board!) Editor Improvements IPS Connect (please note that with the release of IPS Connect our old Converge product will no longer function) SEO Improvements VigLink Integration Best Answer Feature AdminCP Interface Enhancements Bulk Mail with Mandrill Miscellaneous Enhancements IPS CDN Service Anti-Spam Improvements How to Upgrade To upgrade simply log into your client area, click on "Purchases" from the menu and select the community you wish to upgrade and click "Upgrade Now". View the full article