Skocz do zawartości


  1. IPSBeyond

    1. BOU

      BOU - Biuro Obsługi Użytkownika. Tutaj będą zamieszczane ogłoszenia oraz inne ważne informacje dotyczące forum

    2. Propozycje i sugestie

      Tutaj można zgłaszać swoje propozycje i sugestie dotyczące forum i strony

  2. IP.Board Support

    1. Ogólne rozmowy o IP.Board

      Forum przeznaczone jest do prowadzenia ogólnych dyskusji na temat wszystkich wersji IP.Board. W forum tym NIE JEST udzielany żaden support od tego są odpowiednie działy.

    2. 2242
    3. 5652
      • Brak postów
    4. Tworzenie własnych dodatków

      Chcesz stworzyć własny dodatek a masz problem z kodem php lub HTML? Ten dział jest właśnie dla Ciebie.

    5. 445
    6. 12297
  3. Support dodatków

    1. 1275
    2. IP.Nexus

      Dodatki do aplikacji IP.Nexus

    3. IP.Content

      Dodatki do aplikacji IP.Content

    4. 495
    5. 12
    6. 37
    7. 26
    8. 410
  4. Ogólne

    1. Rozmowy Niekontrolowane

      Tutaj możecie porozmawiać na każdy temat bez ograniczeń

    2. Ogłoszenia

      Chcesz coś kupić, sprzedać, zaoferować pracę lub współpracę? ten dział jest do tego stworzony

    3. 553
    4. 674
    5. IPS Community Suite - News

      Najnowsze informacje związane z IPS Community Suite

    6. Spam Room

      Tutaj można przetestować funkcje forum, napisać przykładowy temat. Wypowiedzi w tym dziale nie są naliczane

    7. Kosz

      Wszystko co nie pasuje do żadnej kategorii lub łamało regulamin znajduje się w tym forum

ręcznie malowane bombki
Trzy jajka Komozja Family. Sklep Internetowy Bomboniera.
  • Nasze aplikacje

  • Blog IPSBeyond

  • Posty

    • Witam! Mam problem z userblock... Wszystko mi w nim działa, lecz nie wyświetla się cover photo. Wie ktoś może jak temu zaradzić? [IPS 4.2]

        {{if \IPS\Member::loggedIn()->inGroup( $configuration['userBlock_groups'], TRUE ) || $configuration['userBlock_groups'] == "all"}}     {{$member = \IPS\Member::loggedIn();}}     {{$coverPhoto = \IPS\Member::loggedIn()->coverPhoto();}}          <div class="userBlock">                     {{if $coverPhoto->file}}             <div class="userBlock_coverPhoto overlay">                 <img src='{$coverPhoto->file->url}' class='ipsCoverPhoto_photo euip_CoverPhotoHeight' alt=''>             </div>         {{endif}}         <div class="userBlock_avatar{{if $coverPhoto->file}} withCover{{endif}}">               {template="userPhoto" group="global" app="core" params="$member, 'medium'"}          </div>         <div class="userBlock_info">                <div class="userBlock_name">                 <a href='{$member->url()}' title='{lang="view_my_profile"}'>{{if isset( $_SESSION['logged_in_as_key'] )}}{lang="front_logged_in_as" sprintf="$_SESSION['logged_in_from']['name']"} {{endif}}{member="name"}</a>                 {{if $member->member_title && $member->member_id}}                     <p>{$member->member_title}</p>                 {{elseif $member->rank['title'] && $member->member_id}}                     <p>{$member->rank['title']}</p>                 {{endif}}             </div>                          <div class="userBlock_counters">                 {{if \IPS\Member::loggedIn()->member_id }}                     {{$posts = number_format($member->member_posts);}}                     {{$reputation = number_format($member->pp_reputation_points);}}                                  <a href="{url="app=core&module=members&controller=profile&do=content&id={$member->member_id}" base="front" seoTemplate="profile_content" seoTitle="$member->members_seo_name"}" title="{lang="members_content" sprintf="$member->name"}" data-ipsTooltip>                         {lang="userBlock_postCount"} {$posts}                     </a>                     <a href="{url="app=core&module=members&controller=profile&id={$member->member_id}&do=reputation" seoTemplate="profile_reputation" seoTitle="$member->members_seo_name"}" title="{lang="members_reputation" sprintf="$member->name"}" data-ipsTooltip>                         {lang="userBlock_reputaionPoints"} {$reputation}                     </a>                 {{else}}                     <a href="{url="app=core&module=system&controller=login" seoTemplate="login" protocol="\IPS\Settings::i()->logins_over_https"}">                         {lang="login"}                     </a>                     <a href="{url="app=core&module=system&controller=register" seoTemplate="register"}">                         {lang="sign_up"}                     </a>                 {{endif}}                                     </div>         </div>     </div> {{endif}}  
    • Stripe is the most popular payment method in Commerce, allowing communities to take payments by card securely with easy setup. While there's no doubt that credit cards are still the most popular methods of making a payment, digital innovations such as Apple Pay and Bitcoin are increasing in popularity. For 4.3 we've deepened our integration to support some of their latest features. Apple Pay & Google Pay Apple Pay allows users to pay quickly with their iPhone, iPad or Mac (with Safari and either a paired iPhone or using the MacBook Pro with Touch ID) using the card details stored on the device, authenticated with Touch ID or Face ID. Apple Pay Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself. Paying with card details stored in Google Chrome   Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option. Commerce will automatically hide the option if the user's device does not support either method.   Bitcoin Bitcoin support is also now available. If enabled, after the user chooses the Bitcoin option, the amount to pay is automatically converted into BTC and the user is shown an address to send bitcoins to: Bitcoin Payment Screen After the payment is received, the user will automatically receive an email confirmation.   3D Secure Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes. After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification. Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.   Amex Express Checkout American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3. Amex Express Checkout   Alipay, Bancontact, Giropay, iDEAL, SOFORT These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries). The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back. All of these are also now supported through Stripe in 4.3.   Dispute/Chargeback Handling A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate. Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold). Disputed Transaction All transactions with currently open disputes can be accessed quickly from the transaction list. The transaction page will show you the status and reason for the dispute, and links to your Stripe dashboard where you can respond. When the dispute is resolved, the transaction screen will be updated, with either the transaction being marked as refunded if the dispute is lost, or going back to paid if the dispute is won and the funds returned to you. A dispute that was lost A dispute that was won     Radar Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions. Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally. In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured. In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address. If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn. Wyświetl pełny wpis
    • Do you need to track the activities of specific members on your forum? Track Members will allow you to track the steps of any member as they interface with your forum and it is highly configurable to include settings for time frame and a multitude of trackable actions (Account Actions, Profile Actions, Messenger Actions, Content Actions). It also provides settings for automatic member tracking for members being warned as well as new members. - PERMISSIONS TO USE There are two Moderator permissions to use the application: Can track members? Can view logs from tracked members? - TRACK ACTIONS: Account Actions Sign In, Sign Out, Change password, Change email address, Update personal photo and Upload a cover photo Profile Actions Visit a profile, Follow/Unfollow a member, Ignore/Stop ignoring a member, Post a status update and Reply to a status update Messenger Actions Enable/Disable Messenger, Start a new conversation, Reply to a conversation and Left a conversation Content Actions Visit a content item,  Create new content item, Reply/comment on a content item, Review a content item, React/Unreact to content items, replies/comments and reviews  and Follow/Unfollow content items/categories You can choose which setting will be enabled by default in Settings. Disabled settings will not appear to the moderator in the track popup.   - LOGS Logs will be available on: Admin CP module App index A tab in user profile Only moderators with proper permisison will be able to view the logs   - TRACK/STOP TRACKING You can can track/stop tracking members from: app index member profile member mini profile (hover link)   - COMPATIBILITY Member History: it will be logged the moderator who started and stopped tracking the member Moderator Log: it will be logged the member who is being tracked and also when stopped being tracking   - TOOLS Track all members from specific group for a defined number of days Stop Tracking All Members Prune Logs Prune Orphaned Logs (logs from members currently not being tracked)   - SETTINGS Several settings, such as: Groups to be tracked Flood time control Number of log entries on App index and in ACP module Trackable actions Integration to Warn System: you can track a warned member for a specific number of days New Members: you can track new members for a specific number of days Prune trackings logs management Pobierz plik
    • This application will log and store all registrations and logins to your forum from users using proxy servers. All users registering through suspected proxy servers can be set to be manually approved.  The logs can be pruned based on a number of days criteria. At the logs page, you can search for members to see if they have either registered at your forum or logged in using a suspected proxy server. You can also search for proxy ips, between a certain time frame and as last but certainly not least, you can search for users using proxies by way of registration or log in. Your staff can be notified any time when an user has been registered through suspected proxy servers by way of an automated topic that can be posted at your forum.  This app can come in handy when users that have been banned from your forum can use a proxy server to come back to your forum. Pobierz plik
    • (SD) Live Streams is an application that allows you to present live streaming.   Supported platforms   Functionalities Creating categories with permissions Creating packages Charging for adding streams Internal grant system Channels +18 years (including age verification) Commenting on entries Comments recomendation Messages in streams Chat from platforms The ability to set the cover for the stream The ability to create topics when adding streams   More screens: Demo:       Pobierz plik
  • Najnowsze aktualizacje statusu

  • Statystyki forum

    • Tematów
    • Postów
  • Statystyki użytkowników

    • Użytkowników
    • Najwięcej dostępnych

    Najnowszy użytkownik
  • Informacje o długości życia forum

    • Data uruchomienia forum
      04.01.2008 18:05

Ważne informacje

Kontynuując przeglądanie strony, wyrażasz zgodę na używanie przez nas plików cookies.