NewsBot

We are releasing security patches for IP.Gallery 4.2.1 and IP.Gallery 5.0.5 to address a potential cross-site scripting issue related to the acceptance of SWF uploads. SWF (Shockwave Flash) is a file format used to embed flash movies in HTML documents, and when media files are accepted in IP.Gallery, SWF uploads are allowed. Because SWF files allow arbitrary script to execute within the context of the site they are hosted on, we are releasing a patch today which disables SWF files from being accepted by IP.Gallery by default. You may still allow SWF files after installing this patch by following the instructions in this knowledge base article, however we strongly recommend that you do not allow SWF submissions unless only trusted users are able to submit movies in your IP.Gallery installation. To apply the patch, please perform the following steps: Identify which version of IP.Gallery you are running. Download the appropriate patch file below Extract the contents locally on your computer Upload the contents of the "upload" folder to your forum root directory (where conf_global.php is located), overwriting any files when prompted. Please refer to this knowledgebase article if you are unfamiliar with using FTP to transfer files to your server. If you are an IPS Community in the Cloud customer running IP.Gallery 4.2.1 or above, no further action is necessary; we have already automatically patched your account. If you are using a version older than IP.Gallery 4.2.1, you should contact support to upgrade. If you are running IP.Gallery 4.2.1, please use the following zip: gallery_4.2-patch-Jan_3_2013.zip 5.01KB 6 downloads If you are running IP.Gallery 5.0.5, please use the following zip: gallery_5.0-patch-Jan_3_2013.zip 5.6KB 22 downloads As of the time of this post, the full IP.Gallery package in our client center has been updated. If you are running any version of IP.Gallery that is not listed above, we recommend that you upgrade to the latest version to obtain these security fixes, as well as several other security and bug fixes. We would like to thank Vasil A (Bulgaria) for bringing the vulnerability to our attention. Zobacz cały news

File Name: (MDX) IPB Mobile Improved File Submitter: Andrzej File Submitted: 12 Jan 2014 File Category: IP.Board 3.4 IP.Board 3.4 compatible?: Yes IP.Board 3.3 compatible?: Untested IP.Board 3.2 compatible?: Untested IP.Board 3.1 compatible?: Untested IP.Board 3.0 compatible?: Untested Improved style mobile with additional features! In the style IPB Mobile Improved was changed: Added information about the last post and the author in board index Swapped icons in navigation Added to navigation My content link Added display to comments statuses Added ability to sort threads Added ability to sort statuses Added ability to sort members Enjoy Click here to download this file Pobierz plik

File Name: (MDX) Feel Blue! File Submitter: Andrzej File Submitted: 12 Jan 2014 File Category: IP.Board 3.4 IP.Board 3.4 compatible?: Yes IP.Board 3.3 compatible?: Yes IP.Board 3.2 compatible?: Untested IP.Board 3.1 compatible?: Untested IP.Board 3.0 compatible?: Untested Soft blue skin with elements of gradients. Compatibility IP.Board v3.4.6 IP.Nexus v1.5.8 IP.Content v2.3.6 IP.Downloads v2.5.4 IP.Gallery v5.0.5 IP.Blog v2.6.3 IP.Calendar 3.3.4 IP.Chat 1.4.4 Skin Feel Blue! include:Soft appearance Gradient navigation buttons The new look post and topic count Subforums arranged in two columns New forum icons Icons online and offline Editor fit in the same color skin Text logo Guests message with the ability to collapse New messenger and notifications icons Social icons in header and more... To add links to social buttons must go to ACP -> Look & Feel -> Global Templates -> globalTemplate and find:http://twitter.com/{twitter username}' title='Latest news and updates at twitter'><img src='{$this->settings['img_url']}/twit.png' width='35' height='35' alt='twitter' /></a></li><li style='margin:0px;'><a href='http://www.youtube.com/user/{youtube username}' title='View my Youtube videos'><img src='{$this->settings['img_url']}/yt.png ' width='35' height='35' alt='youtube' /></a></li><li style='margin:0px;'><a href='https://plus.google.com/{google plus id}' title='View our Google Plus page'><img src='{$this->settings['img_url']}/goog.png' width='35' height='35' alt='googleplus' /></a></li><li style='margin:0px;'><a href='https://facebook.com/{facebook username}' title='View FanPage'><img src='{$this->settings['img_url']}/fb.png' width='35' height='35' alt='facebook' /></a></li></ul> Terms & Conditions: To be installed on one forum only, to install on more than one then you will need to purchase skin again (contact me for discounts for purchasing more than one skin). You are not allowed to give free, re-sell or make profit directly from the skin. You do not have the right to redistribute this skin set in any way. Click here to download this file Pobierz plik

File Name: (MDX) WarFare File Submitter: Andrzej File Submitted: 12 Jan 2014 File Category: IP.Board 3.4 IP.Board 3.4 compatible?: Yes IP.Board 3.3 compatible?: Yes IP.Board 3.2 compatible?: Untested IP.Board 3.1 compatible?: Untested IP.Board 3.0 compatible?: Untested Dark transparent skin for war games Compatibility IP.Board v3.4.6 IP.Nexus v1.5.8 IP.Content v2.3.6 IP.Downloads v2.5.4 IP.Gallery v5.0.5 IP.Blog v2.6.3 IP.Calendar 3.3.4 IP.Chat 1.4.4 Skin WarFare include:New look header Subforums arranged in two columns New forum icons Editor fit in the same color skin New messenger and notifications icons Social icons in header Button (under every post) that allows give warn for post and more... To add links to social buttons must go to ACP -> Look & Feel -> Global Templates -> social_icon *In the archive added font used to create the logo Terms & Conditions: To be installed on one forum only, to install on more than one then you will need to purchase skin again (contact me for discounts for purchasing more than one skin). You are not allowed to give free, re-sell or make profit directly from the skin. You do not have the right to redistribute this skin set in any way. Click here to download this file Pobierz plik

File Name: (MDX) Feel Red! File Submitter: Andrzej File Submitted: 12 Jan 2014 File Category: IP.Board 3.4 IP.Board 3.4 compatible?: Yes IP.Board 3.3 compatible?: Yes IP.Board 3.2 compatible?: Untested IP.Board 3.1 compatible?: Untested IP.Board 3.0 compatible?: Untested Soft red skin with elements of gradients. Compatibility IP.Board v3.4.6 IP.Nexus v1.5.8 IP.Content v2.3.6 IP.Downloads v2.5.4 IP.Gallery v5.0.5 IP.Blog v2.6.3 IP.Calendar 3.3.4 IP.Chat 1.4.4 Skin Feel Red! include:Soft appearance Gradient navigation buttons The new look post and topic count Subforums arranged in two columns New forum icons Icons online and offline Editor fit in the same color skin Text logo Guests message with the ability to collapse New messenger and notifications icons Social icons in header and more... Terms & Conditions: To be installed on one forum only, to install on more than one then you will need to purchase skin again (contact me for discounts for purchasing more than one skin). You are not allowed to give free, re-sell or make profit directly from the skin. You do not have the right to redistribute this skin set in any way. Click here to download this file Pobierz plik

You can use this gateway for accept bitcoin from users our access to BTC is limited so IPN callback didn't test please feel free to donate to us well we can test IPN also you'll get an copyright remover for this great gateway Prerequisites Ioncube Loader curl 7.26+ Pobierz plik

Simplistic is a lightweight modern theme,using mainly the flat style of design in keeping with modern web design.I have tried to make this skin as lightweight as possible using little or no images at all.It is also a very neutral theme which would serve any forum or business site very well. Logo psd included Font awesome icons used for various elements of the skin Footer links block looks great on mobile devices and tablets No annoying copyright low price as always Full support offered color picker may be added in future if demand for this is warranted Pobierz plik

This hook will let to users change board font Pobierz plik

Enjoy making fun of pictures? want to bring the fun to your community? With CJ Caption Contest you can. Allows for multiple catgories, commenting, voting on comments, and automation of comment winner when caption expires. Features: unlimited categories unlimited caption moderator creation commenting voting on comments (for caption winning) and much more. check out the demo! Pobierz plik

A few years ago we revolutionised theme editing in IP.Board with the addition of the "Visual Skin Editor". This tool quickly became a popular way of making broad color changes to new themes to match in with an existing site or existing branding. For the first time, you could instantly view the changes you were making. Goodbye Visual Skin Editor, hello Easy Mode Editor. We have rewritten this tool from the ground up in IPS Suite 4.0 and renamed it the Easy Mode Editor now that it's a fully integrated part of the suite and not just a license add-on. It retains all the features you love and has a much better interface, more control and fully supports gradients. Let's take a look! When you create a new theme, you have the option of creating an "Easy Mode" theme or a "Manual Mode" theme. As you would expect, the manual mode allows full editing of CSS and HTML. Easy mode allows you to edit the theme with an instant preview. Once the new theme has been added you can launch it from the Theme list inside the administrator's control panel by clicking the wand button. You can still edit the HTML templates and custom CSS as normal should you need to. The easy mode editor launches in a new browser tab or window (depending on your browser's settings). The floating palette overlay in IP.Board 3 was a little cumbersome as it took up a fair amount of room and you had to move it out of the way to view your changes. In IPS 4, we've made this a fixed sidebar which means that it doesn't have to reload when you navigate through the suite. I've cropped out most of the public display as we're not quite ready to reveal that yet! You can quickly colorise your new theme with the Colorize option. This chromatically changes the main colors of the suite quickly and easily. A limitation of the Visual Skin Editor in IP.Board 3 was that it couldn't manage gradients so themes had those gradients removed and flat color applied. We now support gradients in IPS 4.0 from the Easy Mode Editor's color editing panel. We previously blogged about the fantastic new theme settings feature in IPS 4.0. Some of these settings are now available to editing in the settings panel. This is a really quick and convenient way to change these settings. Although the new Easy Mode Editor allows you to change most of the colors within the suite, there may be times when you want to write a few lines of custom CSS to tweak the theme a little more to your liking. We've got that covered too. You can leave the theme as an Easy Mode theme for as long as you want. However, you may decide that you want a little more control and need to edit some of the framework CSS that underpins the suite. That's easy to do. Just choose the option to convert it to a Manual Mode theme and you are all set. Never before has theming been so simple! This re-invented tool allows you to quickly edit your theme without fuss and you can instantly see the changes as you make them. We can't wait to see what you do with it! Attached Thumbnails Zobacz cały wpis

A few years ago we revolutionised theme editing in IP.Board with the addition of the "Visual Skin Editor". This tool quickly became a popular way of making broad color changes to new themes to match in with an existing site or existing branding. For the first time, you could instantly view the changes you were making. Goodbye Visual Skin Editor, hello Easy Mode Editor. We have rewritten this tool from the ground up in IPS Suite 4.0 and renamed it the Easy Mode Editor now that it's a fully integrated part of the suite and not just a license add-on. It retains all the features you love and has a much better interface, more control and fully supports gradients. Let's take a look! When you create a new theme, you have the option of creating an "Easy Mode" theme or a "Manual Mode" theme. As you would expect, the manual mode allows full editing of CSS and HTML. Easy mode allows you to edit the theme with an instant preview. Once the new theme has been added you can launch it from the Theme list inside the administrator's control panel by clicking the wand button. You can still edit the HTML templates and custom CSS as normal should you need to. The easy mode editor launches in a new browser tab or window (depending on your browser's settings). The floating palette overlay in IP.Board 3 was a little cumbersome as it took up a fair amount of room and you had to move it out of the way to view your changes. In IPS 4, we've made this a fixed sidebar which means that it doesn't have to reload when you navigate through the suite. I've cropped out most of the public display as we're not quite ready to reveal that yet! You can quickly colorise your new theme with the Colorize option. This chromatically changes the main colors of the suite quickly and easily. A limitation of the Visual Skin Editor in IP.Board 3 was that it couldn't manage gradients so themes had those gradients removed and flat color applied. We now support gradients in IPS 4.0 from the Easy Mode Editor's color editing panel. We previously blogged about the fantastic new theme settings feature in IPS 4.0. Some of these settings are now available to editing in the settings panel. This is a really quick and convenient way to change these settings. Although the new Easy Mode Editor allows you to change most of the colors within the suite, there may be times when you want to write a few lines of custom CSS to tweak the theme a little more to your liking. We've got that covered too. You can leave the theme as an Easy Mode theme for as long as you want. However, you may decide that you want a little more control and need to edit some of the framework CSS that underpins the suite. That's easy to do. Just choose the option to convert it to a Manual Mode theme and you are all set. Never before has theming been so simple! This re-invented tool allows you to quickly edit your theme without fuss and you can instantly see the changes as you make them. We can't wait to see what you do with it! Attached Thumbnails View the full article Zobacz cały news

Soft redblue skin with elements of gradients. Compatibility IP.Board v3.4.6 IP.Nexus v1.5.8 IP.Content v2.3.6 IP.Downloads v2.5.4 IP.Gallery v5.0.5 IP.Blog v2.6.3 IP.Calendar 3.3.4 IP.Chat 1.4.4 Skin Feel Red! include: Soft appearance Gradient navigation buttons The new look post and topic count Subforums arranged in two columns New forum icons Icons online and offline Editor fit in the same color skin Text logo Guests message with the ability to collapse New messenger and notifications icons Social icons in header and more... Terms & Conditions: To be installed on one forum only, to install on more than one then you will need to purchase skin again (contact me for discounts for purchasing more than one skin). You are not allowed to give free, re-sell or make profit directly from the skin. You do not have the right to redistribute this skin set in any way. Pobierz plik

Hook that allows you to set which calendars you want to have discussion topics created when new events are added into them. If your after integration with the Calendar Template System, see here. Please read my purchase guide before purchasing, click here to view. Keep up to date with DevFuse mod development and releases. Calendar Topics feature list: Enable / Disable topic creation with one easy setting. Option to bypass calendar moderation, allowing you to create a discussion topics, even if event is yet to be approved. Calendar Topics supports the calendar moderation, if you choose to moderate each new event added, calendar topic will be create the topic whenever you choose to approve event. Set topic author as the event author or set specified author like an administrator. Set the topic title and topic post template is, includes many quick tags with information such as event author, event title, event date, event content, event link and calendar name. All settings and component management conveniently located all in one application overview page. Editing the calendar event will now edit the discussion topic. Hook to now display a link to the discussion topic for events with discussion topics created. Pobierz plik

A little history For many years, IP.Board functioned under a relatively normal model of managing a content's status. A topic, for example, was either unapproved or approved. If a moderator did not like the topic, that moderator could delete the topic. This worked well for many years, but improvements in technology and processes necessitated changes. As IPS software evolved we recognized the need to handle all content throughout the entire suite in a uniform manner, so old concepts like the "trash can" forum were no longer relevant when considering how you work with Gallery images or Download Manager files. Additionally, many sites today employ moderators that they do not wish to entrust with the complete ability to irrevocably delete content, yet they still need the moderator to be able to clean up a mess should it occur. A few years ago, we introduced the concept of "soft delete". In practice what this meant was that when a user soft deleted a topic, the topic would be removed from general view for most users, but the topic would not actually be deleted. Administrators could choose who can view soft deleted topics, and who could "un-delete" the soft deleted topic. Some time after this, the way topics were deleted changed as well (which was now referred to as "hard delete" in contrast to "soft delete"). If a topic was truly deleted, it would not actually be immediately removed from the database. Instead, a flag was set and the topic would be deleted from the database at some future point in time by a task. The idea was that you may need to restore something that was deleted by a moderator...but then, the software already supports a soft-delete concept to account for this, right? When clients proved to be confused with all of the terminology (we can't blame you!), "hard delete" was renamed back to "delete", and "soft delete" was renamed to hidden. Nevertheless, behind the scenes we still had all of the various statuses to account for Content is awaiting approval (unapproved) Content is approved and viewable (approved) Content has been hidden or soft deleted (hidden) Content has been deleted but not removed from the database yet by the task (pending deletion) Content has been deleted and is gone permanently (deleted) And how about 4.0? In reviewing the needs of most admins and how the process of managing the content and your moderator roles works in the real world, we decided to simplify and improve this experience. The 4.0 Suite now has just 4 of the above statuses, and they behave in a manner you would expect. If you require moderator approval of new content, when something is submitted it will be in an unapproved status. If you do not require moderator approval of new content, that content will be approved automatically and immediately viewable. If a moderator has permission to hide content, the moderator will be able to hide any content that has been submitted. The moderator may or may not be able to see content that is hidden, and may or may not be able to restore hidden content to viewable status. (All that depends on Admin settings.) If a moderator has permission to delete content, the moderator will be able to delete content that has been submitted. Upon doing so, the content is immediately and permanently deleted. You can configure your moderators such that they are able to hide content, delete content, or both. As with 3.x, moderators who can see hidden content will be able to review all hidden content in the Moderator Control Panel, and those with permission to restore hidden content will be able to do so from here as well. You will not have to worry about the content you are viewing in the Moderator Control Panel is deleted or hidden, as there is only one status now. This is an example of a very minor change that was made after careful consideration of how the software functions and should "flow" when being used in a real-world situation. It is often the case that the smallest changes can make the biggest impact in the eyes of the users. Zobacz cały news

A little history For many years, IP.Board functioned under a relatively normal model of managing a content's status. A topic, for example, was either unapproved or approved. If a moderator did not like the topic, that moderator could delete the topic. This worked well for many years, but improvements in technology and processes necessitated changes. As IPS software evolved we recognized the need to handle all content throughout the entire suite in a uniform manner, so old concepts like the "trash can" forum were no longer relevant when considering how you work with Gallery images or Download Manager files. Additionally, many sites today employ moderators that they do not wish to entrust with the complete ability to irrevocably delete content, yet they still need the moderator to be able to clean up a mess should it occur. A few years ago, we introduced the concept of "soft delete". In practice what this meant was that when a user soft deleted a topic, the topic would be removed from general view for most users, but the topic would not actually be deleted. Administrators could choose who can view soft deleted topics, and who could "un-delete" the soft deleted topic. Some time after this, the way topics were deleted changed as well (which was now referred to as "hard delete" in contrast to "soft delete"). If a topic was truly deleted, it would not actually be immediately removed from the database. Instead, a flag was set and the topic would be deleted from the database at some future point in time by a task. The idea was that you may need to restore something that was deleted by a moderator...but then, the software already supports a soft-delete concept to account for this, right? When clients proved to be confused with all of the terminology (we can't blame you!), "hard delete" was renamed back to "delete", and "soft delete" was renamed to hidden. Nevertheless, behind the scenes we still had all of the various statuses to account for Content is awaiting approval (unapproved) Content is approved and viewable (approved) Content has been hidden or soft deleted (hidden) Content has been deleted but not removed from the database yet by the task (pending deletion) Content has been deleted and is gone permanently (deleted) And how about 4.0? In reviewing the needs of most admins and how the process of managing the content and your moderator roles works in the real world, we decided to simplify and improve this experience. The 4.0 Suite now has just 4 of the above statuses, and they behave in a manner you would expect. If you require moderator approval of new content, when something is submitted it will be in an unapproved status. If you do not require moderator approval of new content, that content will be approved automatically and immediately viewable. If a moderator has permission to hide content, the moderator will be able to hide any content that has been submitted. The moderator may or may not be able to see content that is hidden, and may or may not be able to restore hidden content to viewable status. (All that depends on Admin settings.) If a moderator has permission to delete content, the moderator will be able to delete content that has been submitted. Upon doing so, the content is immediately and permanently deleted. You can configure your moderators such that they are able to hide content, delete content, or both. As with 3.x, moderators who can see hidden content will be able to review all hidden content in the Moderator Control Panel, and those with permission to restore hidden content will be able to do so from here as well. You will not have to worry about the content you are viewing in the Moderator Control Panel is deleted or hidden, as there is only one status now. This is an example of a very minor change that was made after careful consideration of how the software functions and should "flow" when being used in a real-world situation. It is often the case that the smallest changes can make the biggest impact in the eyes of the users. Zobacz cały wpis

Adds support for audio files from Spotify into the built-in IP.Board [media] bbcode. After installation just copy the link to your forum, example: https://play.spotify...YNCv777ONrbdHsy Pobierz plik

Description: Streamline the moderation process with the use of automatic alerts for when moderators/admins perform moderation actions. Including support for the most common moderator actions such as open topic or delete post. As well as support for pm, email and/or topic alerts. Selected forums and groups can also be excluded from alerts. Compatibility: IP.Board 3.4.x IP.Board 3.3.x Pobierz plik

Description: The design is Dark with Red area's and has many backend Design Features located in the _ipbConfig Template. The custom design settings are as follows: -Rounded Avatars -Text Logo -Guest Message -Navigation Dropdown -DefaultMoreDropdown -StickyTop -Information message -Danger message -Notice message -Success message -Facebook link -Twitter link -Google+ link The design is compatible with: The latest versions of IP Board 3.x, Gallery, Blog, Downloads, Chat, IP.Content and Nexus The skin is compatible with all major, modern browsers including Internet Explorer 8/9, Firefox, Safari, Chrome and Opera. Installation: 1) Go to AdminCP -> Look & Feel -> Import 2) Upload the dark-red.xml file (Skin Files) to Upload XML(Archive) Skin Set 3) Upload the images-dark-red.xml (Skin Files) to Upload XML(Archive) Image Set 4) Upload the replacements-dark-red.xml (Skin Files) to Upload XML Replacements Set If you would like to set Dark + Red as the default design then go to 1) Go to AdminCP -> Look & Feel 2) Click the dropdown for "Dark + Red" 3) Click "Edit Settings" 4) Scroll down to "Make this the default skin?" 5) Click the checkmark 6) Scroll down + save settings I have also included the Usergroup images that i have custom made for this design + the PSD + The text information if you wish to create your own images for additional Usergroup images. Pobierz plik

Improve your community, by providing styled call out boxes. Features: 3 Styles (Will be adding more in the near future!) Well documented Pobierz plik

With this hook you can easily convert message from private conversation to a topic. Starter of the message will be informed on PM about this operation also. Only first message in conversation will be converted to the new topic. In the notification you can add '%s' to replace it by URL to the newly created topic. Pobierz plik

BIPS is one of the largest bitcoin payment solution providers. BIPS operates as a Payment Service Provider (PSP) for Merchants and acquirers bitcoin payments for consumers and merchants. More Prerequisites Ioncube Loader php 5.2.6+ curl 7.26+ you can make a payment from here, please do not pay this, because BIPS don't have sandbod mode Pobierz plik

IPS Connect is our in-house cross-site authentication framework utilized by IP.Board in order to facilitate sharing of login credentials on one or more of your websites. While IP.Board supports Connect out of the box (meaning administrators of two or more IP.Board installations can allow users to use the same login credentials on any site in the network with just a few clicks in the ACP), the design of the system allows for third party software to tie in to the network as well. Indeed, one of the more popular addons in our Marketplace is the Wordpress IPS Connect plugin. We have made several changes to IPS Connect in 4.0 that we believe will help you better manage a network of sites designed to share login credentials amongst them. These changes stemmed both from our own internal use of IPS Connect and from direct user feedback in our feedback forums. Fundamental Improvements In IP.Board 3.4, a "master" installation has no knowledge of any "slave" installations that may call to it. Any IP.Board can be set up to call to the master installation and this mater installation will never remember that the slave has called to it in the future. While this is fine for basic login credential checking, the original design of IPS Connect introduces many limitations. For instance, updating your email address on any given site cannot cause the email address to be updated on all sites because there is no central installation that knows about any of the sites in the network. Similarly, logging in to one site cannot log you in to all sites because all of the sites on the network are not actually known at any one location (we do, however, work around this if all sites are on the same domain). Beginning with 4.0, the master installation will "register" any site that connects to it using IPS Connect. This introduces many benefits: If you make a change on any individual site (master or slave), that change can now be propagated to all other sites in the network. Logging in or out of any given site can log you in to all other sites (because all other sites are now "known") Requests can be queued if there are problems You can create a listing of all sites in the network from the master installation Further, we have thought through potential issues and have implemented a queue system where-by if requests to an individual site in the network begin failing then those requests will be queued and reattempted at a later date in the order they were originally received. If failed requests start queuing on the master installation, an ACP dashboard block will show you this and let you attempt to process them manually. If the issue causing the requests to fail has been resolved, the queue can quickly clear out in this manner (vs waiting for the task to clear them out). If the issue is still occurring, however, you will be given some additional information which will be helpful in determining why the requests are failing. Finally, if the site in question has been taken offline and future requests should not be sent to it, you are given the opportunity to unregister the "slave" installation so that the master will no longer communicate with it. More changes propagated We found while using IPS Connect internally that we wanted certain actions to propagate across all sites on the network but IPS Connect did not handle this, and we subsequently had to develop custom hooks in-house to account for the missing functionality. As a result, with 4.0 IPS Connect will now manage a few additional capabilities. Banning As of 4.0, if you permanently ban a user from the admin control panel, the ban will be copied to the rest of the sites in the IPS Connect network. Bans are only propagated to other sites if initiated via the admin control panel as a security precaution. It is probable in many cases that you do not want moderator actions on one site affecting accounts on another site, so front-end bans will not be copied to other sites. Deleting As of 4.0, deleting users from one site in an IPS Connect network will now cause the user to be deleted on all sites in the network. Merging Similarly, as of 4.0 when you merge two users on a site in an IPS Connect network, the users will be merged on all sites in the network. Password Changes As of 4.0, password changes are fully propagated to all sites in an IPS Connect network. The net effect will be no different than IP.Board 3.4 in this regard, unless you later disable IPS Connect on a site in the network - in this case, the last used password will still be valid on that site, rather than some random password potentially stored on a "slave" installation 5 years ago that the user cannot remember. Cross Domain Logins (and Logouts) Beginning with 4.0, IPS Connect will now support logging in and out across different domains. Cookie restrictions (and the fact that the master installation did not register and/or remember any of the slave installations) prevented this capability with 3.4.x, so while the login credentials could be shared across domains, signing in to one installation did not sign you in to any other installation automatically (unless they were on the same domain). Similarly if you logged out of an installation you were not automatically logged out of any other installation in 3.4.x. As of 4.0, if you sign in to an installation (whether it is the master or an individual slave application), you will be redirected to the master installation, then redirected to each slave application in turn, and finally redirected back to your original destination. This is all very seamless to the end-user and largely unnoticeable. Logging out will, similarly, redirect you to each application to log you out of that application, bypassing security restrictions applied to cookies in a multi-domain environment. Wrapping Up Just as with IP.Board 3.4, other applications can tie in to the IPS Connect network, either as a master installation or as a slave installation. IPS Connect support has otherwise been greatly improved and now offers a much wider range of functionality, a more robust built-in SSO system, and more reliability when problems do occur via the new request queuing system. It should be noted that IPS Connect with 4.0 is NOT compatible with IP.Board 3.4.x, and sites will need to "re-register" with the master so that it can know about them. That minor limitation aside, we believe you will enjoy the great improvements coming in the next release! Zobacz cały wpis

IPS Connect is our in-house cross-site authentication framework utilized by IP.Board in order to facilitate sharing of login credentials on one or more of your websites. While IP.Board supports Connect out of the box (meaning administrators of two or more IP.Board installations can allow users to use the same login credentials on any site in the network with just a few clicks in the ACP), the design of the system allows for third party software to tie in to the network as well. Indeed, one of the more popular addons in our Marketplace is the Wordpress IPS Connect plugin. We have made several changes to IPS Connect in 4.0 that we believe will help you better manage a network of sites designed to share login credentials amongst them. These changes stemmed both from our own internal use of IPS Connect and from direct user feedback in our feedback forums. Fundamental Improvements In IP.Board 3.4, a "master" installation has no knowledge of any "slave" installations that may call to it. Any IP.Board can be set up to call to the master installation and this mater installation will never remember that the slave has called to it in the future. While this is fine for basic login credential checking, the original design of IPS Connect introduces many limitations. For instance, updating your email address on any given site cannot cause the email address to be updated on all sites because there is no central installation that knows about any of the sites in the network. Similarly, logging in to one site cannot log you in to all sites because all of the sites on the network are not actually known at any one location (we do, however, work around this if all sites are on the same domain). Beginning with 4.0, the master installation will "register" any site that connects to it using IPS Connect. This introduces many benefits: If you make a change on any individual site (master or slave), that change can now be propagated to all other sites in the network. Logging in or out of any given site can log you in to all other sites (because all other sites are now "known") Requests can be queued if there are problems You can create a listing of all sites in the network from the master installation Further, we have thought through potential issues and have implemented a queue system where-by if requests to an individual site in the network begin failing then those requests will be queued and reattempted at a later date in the order they were originally received. If failed requests start queuing on the master installation, an ACP dashboard block will show you this and let you attempt to process them manually. If the issue causing the requests to fail has been resolved, the queue can quickly clear out in this manner (vs waiting for the task to clear them out). If the issue is still occurring, however, you will be given some additional information which will be helpful in determining why the requests are failing. Finally, if the site in question has been taken offline and future requests should not be sent to it, you are given the opportunity to unregister the "slave" installation so that the master will no longer communicate with it. More changes propagated We found while using IPS Connect internally that we wanted certain actions to propagate across all sites on the network but IPS Connect did not handle this, and we subsequently had to develop custom hooks in-house to account for the missing functionality. As a result, with 4.0 IPS Connect will now manage a few additional capabilities. Banning As of 4.0, if you permanently ban a user from the admin control panel, the ban will be copied to the rest of the sites in the IPS Connect network. Bans are only propagated to other sites if initiated via the admin control panel as a security precaution. It is probable in many cases that you do not want moderator actions on one site affecting accounts on another site, so front-end bans will not be copied to other sites. Deleting As of 4.0, deleting users from one site in an IPS Connect network will now cause the user to be deleted on all sites in the network. Merging Similarly, as of 4.0 when you merge two users on a site in an IPS Connect network, the users will be merged on all sites in the network. Password Changes As of 4.0, password changes are fully propagated to all sites in an IPS Connect network. The net effect will be no different than IP.Board 3.4 in this regard, unless you later disable IPS Connect on a site in the network - in this case, the last used password will still be valid on that site, rather than some random password potentially stored on a "slave" installation 5 years ago that the user cannot remember. Cross Domain Logins (and Logouts) Beginning with 4.0, IPS Connect will now support logging in and out across different domains. Cookie restrictions (and the fact that the master installation did not register and/or remember any of the slave installations) prevented this capability with 3.4.x, so while the login credentials could be shared across domains, signing in to one installation did not sign you in to any other installation automatically (unless they were on the same domain). Similarly if you logged out of an installation you were not automatically logged out of any other installation in 3.4.x. As of 4.0, if you sign in to an installation (whether it is the master or an individual slave application), you will be redirected to the master installation, then redirected to each slave application in turn, and finally redirected back to your original destination. This is all very seamless to the end-user and largely unnoticeable. Logging out will, similarly, redirect you to each application to log you out of that application, bypassing security restrictions applied to cookies in a multi-domain environment. Wrapping Up Just as with IP.Board 3.4, other applications can tie in to the IPS Connect network, either as a master installation or as a slave installation. IPS Connect support has otherwise been greatly improved and now offers a much wider range of functionality, a more robust built-in SSO system, and more reliability when problems do occur via the new request queuing system. It should be noted that IPS Connect with 4.0 is NOT compatible with IP.Board 3.4.x, and sites will need to "re-register" with the master so that it can know about them. That minor limitation aside, we believe you will enjoy the great improvements coming in the next release! Zobacz cały news

Amazon Advanced Simple Pay is an easy way to accept payments or donations and makes it possible for hundreds of millions of Amazon customers to pay conveniently and securely on your website using the information in their Amazon accounts. (more) FAQ Features Get to know more of your customers. Help increase conversion with fewer clicks Extend your relationship beyond the transaction Mobile-ready Proven Fraud Protection No add-on fees, period Prerequisites Ioncube Loader php 5.2.6+ curl 7.26+ you can test it from here, you'll need an amazon sandbox account for testing Pobierz plik

This is my first skin for Invision Power Board that I have decided to release. Music is a theme I created for my own personal website, and I decided I would go ahead and share it with the public. The theme is compatible with Invision Power Board v.3.4.x I hope you enjoy this theme, and provide feedback for any future skins I may release. Thanks! ~Clayton Fogg Pobierz plik