Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Earlier
  3. Askancy

    Installazione di IP.Suite 4.x

    Prima di effettuare qualsiasi tipo di aggiornamento, consigliamo gli utenti di effettuare un backup dei file e del database. Installazione pulita di Invision Community Assicurarsi che il server soddisfi i requisiti di sistema con il tool di verifica. Scaricare l'ultima versione del software dall'area client. Decomprimere il pacchetto zip e caricare i file Adesso non ci resta che aprire il browser e recarci alla pagina in cui abbiamo caricato il nostro IP.Suite, per trovarci di fronte questa schermata. Una volta cliccato su Start Installation (Inizia Installazione), ci verranno elencati tutti i requisiti PHP per poter portare a termine l'installazione del software. In "File System Requirements" invece, troviamo l'elenco delle cartella cui dobbiamo cambiare i permessi per poterci salvare/scrivere file, immagini e altri dati. Se siete arrivati fin qui dovresti ben sapere che IP.Suite per poter essere utilizzata necessita di una licenza, acquistabile dal sito ufficiale. Adesso non vi resta che inserire la licenza che vi è stata fornito subito dopo l'acquisto. N.B. La chiave è univoca e non può essere utilizzata contemporaneamente su più . Adesso potete selezionare le applicazioni che avete acquistato con la licenza, nel select potete scegliere l'applicazione di default, ossia quella che partirà non appena un utente inserisce l'url pulito del vostro sito. Nel nostro caso avendo una licenza completa, possiamo installare tutti i software e come app di default lasciamo Forums. Adesso arriviamo alla parte più tecnica ma comunque sia niente di complicato. In questa pagina dobbiamo inserire i dati MySQL che ci sono stati forniti dall'hosting o che abbiamo creato noi stessi dal pannello di controllo o phpmyadmin. Host - Solitamente qui si lascia localhost Username - Inserire l'user del mysql (solitamente root o il nome che si usa per accedere al pannello di controllo dell'hosting) Password Database Name - Nome del database in cui si vuole installare il software Porta - Lasciare 3306 Socket - Lasciare quella preimpostata Table Prefix - Qui è consigliato lasciarlo vuoto, ma se si ha a che fare con un progetto grosso e nel database ci sono altre tabelle per altri vostri script, questa funzione vi permette di dare un prefisso alle tabelle, ad esempio: forum_user Adesso dobbiamo creare il primo utente del forum, quello che sarà il vostro account con cui potrete amministrare IP.Suite. In questo momento non vi resta che attendere che il software esegua tutti i procedimenti per terminare la registrazione, il tempo varia a seconda dell'hosting utilizzato. Cliccando su Go To The Suite avrei modo di vedere il tuo Forum.
  4. Version 1.0.0

    0 downloads

    Questo tool di permetterà di verificare se il tuo hosting dispone dei requisiti di sistema per l'installazione di IP.Suite 4.*.
  5. Askancy

    Glossario dei Termini di IP.Suite

    Invision Power Suite è uno strumento molto potente che ti permette di creare la tua community con estrema semplicità e comodità. Grazie a Invision Power Suite potrai creare un portale e un forum e ampliarlo con tantissime mod create dalla comunità. Per migliorare la tua esperienza in Invision Power Suite e su InvisionITA, ti sarà utile conoscere diversi termini e le abbreviazioni che troverai molto spesso. AdminCP / ACP = Pannello di controllo amministrativo della IP.Suit back-end. Membro = Qualsiasi account registrato nel sistema Gruppo membri = Permessi di controllo e impostazioni per membri assegnati a un determinato gruppo. Tutti i membri fanno parte di uno o più gruppi membri. Ospite = Persona che sta visitando la community senza essere registrato o senza aver effettuato l'accesso. Admin = Persona con accesso all'AdminCP/ACP Moderatore = Membro che ha il permesso di eseguire qualsiasi tipo di controllo sui post degli altri membri sul front-end. Permessi = Tutta la community si basta su permessi. Tramite l'AdminCP potrai creare eccezioni e permessi esclusivi per gruppi di membri.
  6. najaru

    Separare i topic importanti

    Per creare una netta separazione tra i topic importanti e quelli normali è possibile eseguire queste modifiche: ACP -Look & Feel -> Manage Skin Sets & Templates > scegli la skin -> Templates ->Forum View -> forumIndexTemplate. Trovare <table class='ipb_table topic_list' summary='{$this->lang->words[' forum_topic_list ']} "{$forum_data['name ']}"' id='forum_table'> Cancellare queste linee <tr class='header'> <th scope='col' class='col_f_icon'> </th> <th scope='col' class='col_f_topic'>{$this->lang->words['forum_topic']}</th> <th scope='col' class='col_f_starter short'>{$this->lang->words['forum_started_by']}</th> <th scope='col' class='col_f_views stats'>{$this->lang->words['forum_stats']}</th> <th scope='col' class='col_f_post'>{$this->lang->words['forum_last_post_info']}</th> <if test="topicsismod:|:$this->memberData['is_mod'] == 1"> <th scope='col' class='col_f_mod short'> <input type='checkbox' id='tmod_all' class='input_check' title='{$this->lang->words[' topic_select_all ']}' value='1' /> </th> </if> </tr> Poi trovare <!-- BEGIN TOPICS --> poco sopra il begin topic inserire il codice seguente tra l'ultimo if di chiusura e l'ultimo tr di chiusura <!-- Addition for pinned topics separator; Wim G 2010-02-13; BEGIN PART1--> <tr class='header'> <th scope='col' class='col_f_icon'> </th> <th scope='col' class='col_f_topic'>{$this->lang->words['forum_topic']}</th> <th scope='col' class='col_f_starter short'>{$this->lang->words['forum_started_by']}</th> <th scope='col' class='col_f_views stats'>{$this->lang->words['forum_stats']}</th> <th scope='col' class='col_f_post'>{$this->lang->words['forum_last_post_info']}</th> <if test="topicsismod:|:$this->memberData['is_mod'] == 1"> <th scope='col' class='col_f_mod short'> <input type='checkbox' id='tmod_all' class='input_check' title='{$this->lang->words[' topic_select_all ']}' value='1' /> </th> </if> </tr> e poco sotto, subito dopo questo: <if test="hastopics:|:is_array( $topic_data ) AND count( $topic_data )"> {parse striping="forumTable" classes="row1,row2"} <foreach loop="topics:$topic_data as $tid => $data"> aggiungere <!-- Addition for pinned topics separator; Wim G 2010-02-13; BEGIN PART2--> <if test="!$this->subHeadShow"> <tr class='subhead altbar'> <th scope='col' colspan='<if test="endannouncements:|:$this->memberData[' is_mod '] == 1">6<else />5</if>'> <if test="$data['pinned']"> Discussioni importanti <else /> Discussioni </if> </th> </tr> <tr class='header2'> <th scope='col' class='col_f_icon'> </th> <th scope='col' class='col_f_topic'>{$this->lang->words['forum_topic']}</th> <th scope='col' class='col_f_starter short'>{$this->lang->words['forum_started_by']}</th> <th scope='col' class='col_f_views stats'>{$this->lang->words['forum_stats']}</th> <th scope='col' class='col_f_post'>{$this->lang->words['forum_last_post_info']}</th> <if test="topicsismod:|:$this->memberData['is_mod'] == 1"> <th scope='col' class='col_f_mod short'> <input type='checkbox' id='tmod_all' class='input_check' title='{$this->lang->words[' topic_select_all ']}' value='1' /> </th> </if> </tr> <if test="$this->subHeadShow=1"> </if> </if> <if test="$data['pinned']"> <if test="$this->hasPinned=1"> </if> <else /> <if test="$this->hasPinned"> <if test="$this->hasPinned=0"> </if> <tr class='subhead altbar'> <if test="$this->memberData['is_mod'] == 1"> <th scope='col' colspan='6'> <else /> <th scope='col' colspan='5'> </if> Forum Topics </th> </tr> <tr class='header2'> <th scope='col' class='col_f_icon'> </th> <th scope='col' class='col_f_topic'>{$this->lang->words['forum_topic']}</th> <th scope='col' class='col_f_starter short'>{$this->lang->words['forum_started_by']}</th> <th scope='col' class='col_f_views stats'>{$this->lang->words['forum_stats']}</th> <th scope='col' class='col_f_post'>{$this->lang->words['forum_last_post_info']}</th> <if test="topicsismod:|:$this->memberData['is_mod'] == 1"> <th scope='col' class='col_f_mod short'> <input type='checkbox' id='tmod_all' class='input_check' title='{$this->lang->words[' topic_select_all ']}' value='1' /> </th> </if> </tr> </if> </if> dovrebbe essere poi seguito da un altro if di apertura Il risultato è questo:
  7. najaru

    Cambiare redirect dopo il logout

    Qualcuno potrebbe voler gestire in modo diverso la disconnessione dell'utente, facendolo ridirezionare su una pagina diversa dalla home del forum aprire questo file /admin/applications/core/modules_public/global/login.php: return array( 'redirect', $this->lang->words['thanks_for_logout'], $this->settings['base_url'] ); cambiare questo valore '$this->settings['base_url']' con il link della pagina a cui volete venga ridirezionato esempio: return array( 'redirect', $this->lang->words['thanks_for_logout'], 'http://www.invisionita.it/forum/page/sitoweb' );
  8. najaru

    Cambiare redirect dopo il logout

    Qualcuno potrebbe voler gestire in modo diverso la disconnessione dell'utente, facendolo ridirezionare su una pagina diversa dalla home del forum aprire questo file /admin/applications/core/modules_public/global/login.php: return array( 'redirect', $this->lang->words['thanks_for_logout'], $this->settings['base_url'] ); cambiare questo valore '$this->settings['base_url']' con il link della pagina a cui volete venga ridirezionato esempio: return array( 'redirect', $this->lang->words['thanks_for_logout'], 'http://www.invisionita.it/forum/page/sitoweb' ); Visualizza tutto record
  9. najaru

    Ordinare le emoticon in ordine alfabetico

    Chi fosse interessato ad avere le emoticon i ordine alfabetico deve editare questo file: /admin/applications/forums/modules_public/ajax/emoticons.php cercare: $this->DB->build( array( 'select' => 'typed, image', 'from' => 'emoticons', 'where' => "emo_set='".$this->registry->output->skin['set_emo_dir']."'" ) ); e sostituire con: $this->DB->build( array( 'select' => 'typed, image', 'from' => 'emoticons', 'where' => "emo_set='".$this->registry->output->skin['set_emo_dir']."'", 'order' => 'image' ) );
  10. Askancy

    Icone personalizzate nei Forum

    InvisionPower mette a disposizione dell’utente innumerevole personalizzazioni tra cui la possibilità di personalizzare le icone dei forum per rendere il forum più intuitivo e piacevole da usare. Di default IPS4 utilizza le icone del pacchetto FontAwesome, impiegate già nei badges letto/da leggere, ma oltre a questo permette anche di caricare delle icone da file png/jpg e altri formati immagine. Quale metodo conviene usare? E perché? Usare icone FontAwesome Per utilizzare le icone FontAwesome sarà richiesto di modificare il CSS, inserendo delle righe con l’attributo dell’ID del forum. Anche se il processo non è complesso, questo richiede di lavorare con caratteri Unicode. Sarà sufficiente: Scegliere l’icona dalla pagina di FontAwesome Individuare nella pagina il carattere Unicode, che sarà simile a f509 Andare in: Admin CP->Personalizzazione->Tema e cliccare modifica Aprire la directory Core->custom->custom.css In questo file css andremmo a scrivere il nostro css personalizzato in modo che non verrà sostituito nel caso si effettui l’upgrade della board. Il codice che andremmo a scrivere al suo interno sarà: [data-forumid="IDForum"] .fa-comments:before { content: "\f509"; } Nel nostro caso, avendo il forum con l'id 19, il risultato sarà: [data-forumid="19"] .fa-comments:before { content: "\f509"; } [data-forumid="22"] .fa-comments:before { content: "\f1b9"; } Usare icone immagine Per utilizzare le icone immagine sarà sufficiente scaricare una delle tante icone che possiamo trovare facilmente su internet, in ogni caso, ecco un piccolo elenco di siti: https://www.flaticon.com/ https://icons8.com/icons Adesso sarà sufficiente andare in Modifica Forum -> Icon e selezionare l’icona scaricata. N.B. Si raccomanda l’utilizzo di icone 32x32 con sfondo trasparente Quale metodo usare? Il metodo da utilizzare è a discapito dell’amministratore. Se un forum utilizza una sola skin è consigliato l’utilizzo delle icone a immagine avendo a disposizione tantissimi generi di icone. Se un forum invece ha più di una skin tra le scelte dell'utente, come ad esempio una chiara e una scura, è consigliato l’utilizzo delle icone nel css in modo da poter personalizzare il colore dell’icona o del suo background in base alla skin scelta dall'utente.
  11. Additional Information Security Fixed an XSS concern deleting members in the AdminCP. Fixed an XSS concern managing Downloads versions from the changelog view. Fixed a minor XXE possibility in blog RSS imports. Core Upgraded CKEditor to 4.11.4. Updated LinkedIn login handler to use the LinkedIn v2 API. Improved performance when merging two comments with duplicated member reactions for large sites. Improved performance when working with edit history logs. Improved security of how passwords are handled in the code to decrease the likelihood of a password being included in an error log. Improved the display of the upgrader confirmation page. Improved performance of the latest activity stream shown on user profiles. Improved anonymous log in tracking to resolve an issue with "Since my last visit" activity streams Improved the UX configuring moderator permissions for clubs, including the ability to disable club-level moderators. Improved database error reporting in certain error situations. Improved performance of a 4.1.8 upgrader step. Changed AdminCP notifications for "A new member has completed registration" and "A member is flagged as a spammer" to show all applicable members grouped into a single notification, rather than a separate notification for each member. This change gives a significant performance improvement for sites which have lots of new registrations. Fixed multiple formatting concerns with custom profile fields. Fixed an issue where restoring soft-deleted content would throw an exception under specific circumstances ( e.g. when there was no record in the soft deletion log ). Fixed an issue where the member group restriction to require one piece of approved content before users can bypass content moderation was not correctly applied to posts made before registering. Fixed an issue where deleting a member's content and then deleting the member may result in the content not being removed. Fixed SVG images breaking when served through the built in image proxy. Fixed an issue with profile completion if you choose not to upload a profile photo. Fixed third party processor information not showing when users are forced to reaccept an updated privacy policy. Fixed the "Remove followers from uncommented content" setting not working. Fixed an issue where clicking to delete a member twice might result in all status updates being removed from the search index. Fixed an issue where copying content from one area with an attached image and pasting into another area may result in a broken image. Fixed an issue where allowing a user to moderate comments, but not items, would result in an error when using the multi-moderation menu. Fixed inability to edit profile fields by members if the field was not displayed on the profile. Fixed invalid HTML in the quick search form. Fixed an issue where a comment or post made before registering which requires moderator approval after the registration is completed may not update the container flag to indicate that comments within the container require approval. Fixed an error where the member view in the AdminCP may become broken if the member history for the user includes an old subscription group change and Commerce is not installed. Fixed an issue where broken letter photos may be displayed in emails. Fixed an issue with clean up tasks where they may try to delete a member that doesn't exist. Fixed an error that can occur if you double click the "unfollow" button quickly. Fixed autosaved content in the editor not clearing out when it was deleted within the editor. Fixed an issue where MFA while the login would send 3 'new device' emails to the member instead of only one. Fixed an issue where attachment links inserted into content may have a hard coded URL. Fixed an upgrade issue where custom file storage configurations in 3.x may not be preserved correctly when upgrading to 4.x. Fixed an uncaught exception when visiting a specifically malformed follow link. Fixed attachment bbcode tags not converting correctly when upgrading from version 2.0 or older. Fixed the About Me default custom field not showing on new installs. Fixed email statistic charts so they report more accurately. Fixed issues with performing advanced member searches in the AdminCP when multi-select custom profile fields are present. Fixed a minor inconsistency with group name formatting. Fixed an issue rebuilding certain meta data in Elasticsearch. Fixed an issue where items and comments queued for deletion or submitted by a guest prior to registration are returned via the REST API. Fixed an error when searching a specific search string. Fixed a possible error that can occur during login when using the post before register feature. Fixed the Notification Settings form in the Admin CP so that it can save properly. Fixed an issue where Login Handlers were shown out of order. Fixed an issue where the canonical link HTML tag may include unnecessary query string parameters (i.e. filters). Fixed an issue where AdminCP settings search results were not always highlighted when clicked on. Fixed an issue where the pagination for comment and review areas wouldn't link directly to the comments area when Javascript is disabled. Fixed an issue where content item and comment widgets would show content from not specified categories. Fixed an issue where editor auto saved content may not be removed. Fixed an issue where some content may not show a report link. Removed the hide signatures toggles from guests when they are able to see signatures. Prevented search engine spiders from following the cookie notice dismissal link. Removed poll votes from showing in the All Activity stream. Removed ability to copy theme settings. Removed the unread indicator in several widgets because it can't be used there because of the widget cache. Removed the ability to toggle cover photos in clubs list when no image was uploaded. Fixed an issue where the support tool could incorrectly report undiagnosed problems. Fixed missing images when lazy loading is enabled in several areas. Fixed an HTML validation issue with mini-pagination next to multi-page content item titles. Fixed an uncaught exception which is thrown by the Admin Notification System. Fixed member validation display issue in ACP notifications page while mobile. Fixed attachments being added to an editor which has attachments disabled. Fixed an issue where a display name sync error may be displayed on the AdminCP member profile. Fixed two language strings where countries have changed their names: Macedonia is now North Macedonia and Swaziland is now Eswatini. Fixed some broken messenger related links. Core - Clubs Fixed "Clubs" tab showing when splitting content even if clubs are disabled. Fixed display issue with club tabs on mobile devices Removed ability to reorder club tabs on mobile devices Forums Fixed a duplicated error code in the topics REST API endpoints. Fixed images used in forum rules not displaying when image lazy loading is enabled. Fixed a potential upgrade error when reformatting forum rules during the 4.0.0 upgrade routine. Commerce Added an additional subtotal language phrase to the cart summary for localization flexibility. Improved legacy parser to potentially allow conversions of tables in content. Changed renewal terms to not allow $0 renewals. Fixed an error occurring submitting new tickets when read/write database separation is enabled. Fixed an issue where up/downgrading a purchase could result in an error or the expiry date changing incorrectly. Fixed an issue where a cancelled subscription may still generate a renewal invoice (and subsequently charge the user). Fixed tax class being lost with renewal terms in some cases. Fixed an issue where images may not show in printable invoices if lazyload is enabled. Fixed support stream date-based filters producing incorrect results. Fixed stock action text not defaulting in the form when creating a new ticket from the AdminCP if you do not use a signature. Fixed an issue where the password field on the store checkout form might disappear if using Chrome's password autofill feature. Fixed an issue where invoices may not have a billing address set when one is available. Fixed an issue where a template error may be thrown for non-recurring subscriptions. Fixed a missing language string if you had servers configured prior to upgrading to 4.4. Fixed adding a custom package to an invoice. Fixed an exception being logged when rebuilding the search index if any custom packages have been created. Fixed the PayPal Billing Agreements radio element not showing selected if BAs are enabled. Fixed an issue where files uploaded to a custom field may not be downloadable. Removed a stray HTML end tag. Restored Braintree gateway option. Included a disclaimer about qualification process. Pages Fixed an issue where cloning a custom field would result in a database error. Fixed an issue on the media page where the "File Overview" Tab was not set as activated and also not clickable when one or more files from the file list were selected. Added last modified date to database category and record sitemaps. Gallery Changed the reputation type flag for album comments and reviews to resolve bugs where the reputation may be mistakingly treated as if it belongs to an image comment or review. Fixed an issue submitting images to an album if the category requires moderator approval. Fixed an error that can occur when downloading the original image in Gallery if the original image is missing on disk by forcing the largest available size to download instead. Fixed image lazy loading not working correctly in category rules, descriptions and custom error messages. Fixed the submission dialog box potentially showing an incorrect dialog title. Fixed an issue where uploaded videos could not be played in the lightbox. Fixed editor showing twice for each image during submission. Downloads Added a group setting that will allow users to bypass download restrictions when downloading a file that's been purchased. Added the ability to shut off version numbers per-category. Improved the header styling on the homepage. Improved performance, especially of the index page. Reduced top spacing (margin) of the sidebar when viewing the index page. Fixed an issue where custom fields may show out of order. Blog Fixed an issue where the previous and next link under the blog entry could link to hidden or soft deleted entries. Fixed some minor UI issues with the "Blogs" widget. Calendar Added an option to prevent edits and RSVPs for events that have passed. REST & OAuth Fixed the search REST API endpoint. Converters Improved vBulletin archive redirects. Improved vBulletin blog conversions to retain the date the blog or blog entry was followed. Fixed an issue where converted members won't be marked as completed. Fixed an issue when trying to convert from a platform with converters for apps that are not installed. Fixed an issue where PM replies may be duplicated when converting from vBulletin. Fixed an issue with converting comments from Vanilla. Upgrader Fixed an edge case issue where some legacy customers may be unable to use the AdminCP upgrader. Changes affecting third-party developers and designers Backwards-incompatible changes that may affect third party applications / plugins: Methods that handle passwords in login handlers (authenticateUsernamePassword(), authenticatePasswordForMember(), changePassword()) now receive an object which can be cast to a string, rather than a normal string, for the password. This reduces the likelihood of a password being included in an error log. The onPassChange MemberSync callback now receives an object which can be cast to a string, rather than a normal string, for the password. This reduces the likelihood of a password being included in an error log. Enhancements / fixes for developers: Added a new constant \IPS\DEV_LOG_HEADERS which allows you to log all headers being sent during responses. Better abstracted code that dynamically builds class paths for areas that are no longer using iterators. Improved some extension skeleton files to not cause a ParseError once the extension is created. Fixed color fields not initializing for new rows added in a manageable matrix. Fixes that only affect developer mode or third party apps/plugins: Fixed some functions not being called from the root namespace and throwing warnings when in developer mode. Fixed an undefined index loading form to add a new hosting server in Commerce. Code-level fixes that may have been causing bugs in third party apps/plugins: Added code comments to all of the default constant values in init.php explaining what they all do. Ensured all default wizard instances are cast as a string before being sent to the output handler. Fixed an issue when pluralization and sprintf functionality is used together and the placeholder is used in the pluralized string. Fixed an issue with post before register where it was assumed content items would have a container. Fixed an exception when post before registering is checked against a content item that supports reviews but not comments. Fixed some ambiguous column concerns with the \IPS\Content\Item::_comments() method. Fixed an issue editing titles via Ajax when the item class does not use containers. Fixed an issue where the release date may not show correctly for third party plugins or themes. Fixed some functions not being called from the root namespace and throwing an IN_DEV warning. Fixed the widget configuration form being called twice which may result in some form elements duplicating. Improved some extension skeleton files to not cause a ParseError once the extension is created.
  12. Alp_Vampire

    Cambiare skin mobile

    Ottima guida come sempre.. semplice e dettagliata.. Ti ho rotto le scatole, ma tu sei fin troppo paziente.. Grazie Najaru Alessio
  13. najaru

    Cambiare skin mobile

    Se si vuole installare una nuova skin mobile è necessario innanzitutto rendere inattiva la skin mobile di base. Per fare questo è necessario cliccare su Look&Fell - Manage skin set and template - sulla righa della skin mobile da disattivare cliccare sull'icona a destra - edit setting - Select ALL current and future groups or... togliere la spunta e poi nel selettore sotto selezionare esclusivamente un gruppo esclusivo come gli admin o i banned, poi in Hide this skin from the drop down list? mettere si in modo che la skin non sia selezionabile da nessuno. Salvare. Di nuovo nell'icona a destra Manage User Agent Mapping , deselezionare tutto e salvare. Ora la skin mobile vecchia non è più attiva. Per installarne una nuova basta installarla normalmente (se si vuole modificare quella originale è sufficiente esportarla prima, e poi reimportarla cambiando un po il nome), cliccare di nuovo sull'icona a destra e poi Select ALL current and future groups or... cliccare la casella, Hide this skin from the drop down list? mettere NO, poi aprire nuovamente Manage User Agent Mapping ed attivare: Blackberry iPhone iPod Touch Sony Ericsson Nokia Motorol Samsung, Nexus(Google)/Android/HTC LG Palm
  14. najaru

    Cambiare skin mobile

    E figurati Se non volevo farmi rompere le scatole non aprivo un forum di supporto come questo A me rompono le scatole solo gli utenti maleducati o che cercano di prendermi per fesso
  15. Se volete visualizzare un codice solo in determinati forum, andate in boardindextemplate e usate: <if test = "in_array ($ this-> request ['f'], array (XX, YY, ZZ))"> CODICE </ if> dove XX YY ZZ sono gli id dei forum se il forum è solo uno la stringa diventa: <if test = "$ this-> request ['f'] == XX"> CODICE </ if> [source]Adriano Faria[/source]
  16. najaru

    Personalizzare il link per l'accesso admin

    Tutti sappiamo che l'accesso alla cartella admin sulla nostra board avviene aggiungento admincp alla fine dell'url di base. Quindi tutti potrebbero accedere, anche se non conoscono i dati di accesso all'admin comunque Si può rendere più sicura questa cartella dandole un nome diverso, seguendo questa procedura: 1-via FTP rinominare la cartella admin con un nome complesso, ad esempio admin_ty546r3, che nessuno può conoscere. 2-nella root del forum trovare il file initadata.php, aprirlo modificandolo, trovare la linea: define( 'CP_DIRECTORY', 'admin' ); e modificarla inserendo il nuovo nome define( 'CP_DIRECTORY', 'admin_ty546r3' ); ovviamente poi l'accesso all'admin andrà fatto con il nuovo url aggiornato col nuovo nome, oppure tramite l'accesso classico della barra admin nel front end della board La procedura è abbastanza semplice ma attenzione,in tutti gli upgrade futuri (o durante l'installazione di qualsiasi prodotto) bisognerà sempre rinominare la cartella admin che carichiamo con il nuovo nome che abbiamo scelto. Durante gli upgrade della board verrà anche sovrascritto il file initdata.php, quindi quello andrà ri-modificato.
  17. najaru

    Cambiare dominio al forum

    Se si volesse modificare l'URL al vostro forum, ci sono alcune cose da fare per assicurarsi che tutto venga modificato in modo corretto. In primo luogo, spostare il forum sul server nuovo (o dominio nuovo) o nella nuova cartella sul server stesso. Una volta fatto, ecco i passaggi da eseguire: 1. Modificare il file conf_global.php. Aprire il file in un editor di testo e cercate questa linea: $ Info [ 'board_url'] = 'http://www.invisionita.it/forum'; Cambiare l'indirizzo sul lato destro al nuovo URL. Assicurarsi di non aver messo la barra finale, o 'index.php' . Salvare e caricare il file. 2. Accedi al tuo Admin CP e andare alla pagina delle impostazioni di sistema nel tab di system setting , e quindi fare clic sul gruppo di General Configuration. Aggiornare i valori di "Upload URL" e "Path to 'upload' directory'". Assicurarsi che questi valori siano corretti per la vostra nuova posizione. 2 bis. Se avete la IP.Blog, IP.Gallery, o IP.Downloads installati, controllare le impostazioni anche di queste applicazioni. 3. Potrebbe essere necessario modificare le impostazioni del cookie e, guarda la sezione "Cookies" nella pagina delle impostazioni di sistema. 4. Tutti i dati nei post del tuo forum a cui si riferisce alla posizione precedente non saranno più validi, questo include i collegamenti ipertestuali e le emoticon. Questi possono essere fissati eseguendo questa query semplice: UPDATE ibf_posts SET post=REPLACE(post, 'old url', 'new url') Sostituire il 'old_url' e 'new_url' con il vecchio URL e l'URL del vostro nuovo sito, rispettivamente. 5. Assicurarsi di ricontrollare tutte le CHMODs per le cartelle per garantireche tutto funzioni correttamente. I tuoi file caricati e la cartella di cache dovrebbe assolutamente avere il CHMOD tutte le loro sottocartelle ei file impostato a 777 (o 755, a seconda delle esigenze vostro hosting, chiedere a loro se non si è sicuri). Le directory come style_images e style_avatars può essere necessario , consultare la documentazione IP.Board per un elenco completo dei requisiti CHMOD. 6. Sarebbe utile ricostruire tutte le cache, compresi le cache skin. È possibile ricostruire la cache skin facendo Look & Feel -> Template Tools , e fare recache skin set. Vostri file di cache di altri possono essere ricostruiti, Tool setting, Recount & Rebuild, e fare ciascun rebuild.
  18. najaru

    Colorare i nomi degli utenti nei topic

    È possibile colorare i nomi degli utenti in base al colore dei gruppi a cui appartengono (da un post di Mat (FDNZ)) Admin CP > Look and Feel > [Your Skin Here] > Edit Templates & CSS > Topic View > topicViewTemplate e trovare <span class="author vcard"><a class="url fn" href='{parse url="showuser={$post['author']['member_id']}" base="public" template="showuser" seotitle="{$post['author']['members_seo_name']}"}'>{$post['author']['members_display_name']}</a>{parse template="user_popup" group="global" params="$post['author']['member_id'], $post['author']['members_seo_name']"}</span> E sostituire con: <span class="author vcard"><a class="url fn" href='{parse url="showuser={$post['author']['member_id']}" base="public" template="showuser" seotitle="{$post['author']['members_seo_name']}"}'>{IPSLib::makeNameFormatted($post['author']['members_display_name'],$post['author']['member_group_id'])}</a>{parse template="user_popup" group="global" params="$post['author']['member_id'], $post['author']['members_seo_name']"}</span>
  19. luca314

    Icone per forum

    Bene, bravo per l'impegno che ti sei assunto così porti avanti un lavoro che ritengo utile e importante. Per quanto riguarda le icone, per me effettivamente è sufficiente la prima soluzione visto che uso una sola skin. Grazie ancora
  20. Askancy

    Icone per forum

    Quello che mostra IPB nella sua documentazione usa icone provenienti da un file css e font con FontAwesome, quello usato da me invece, fa uso di icone a formato immagine. Solitamente il metodo di IPB si utilizza quando in un forum si utilizzano piu skin, una chiara e una scura per esempio, così da mettere le icone personalizzate per skin. Il metodo usato da me invece, sono per i forum monoskin... Nel caso tu abbia bisogno del metodo di IPB, dimmelo che provo a spiegartelo più semplicemente. Adesso che ho preso il comando di InvisionITA mi sto impegnando a riordinare le guide presenti nel forum e a tradurre quelle ufficiali per rendere il servizio più completo...
  21. luca314

    Icone per forum

    Grazie, io ho provato ad usare le istruzioni contenute nella guida: https://invisioncommunity.com/4guides/themes-and-customizations/tips-tricks_362/changing-fontawesome-icons-per-forum-r164/ Ora sinceramente non so la differenza col metodo che hai usato, ma mi sembra tutto molto più semplice allora…
  22. Askancy

    Icone per forum

    Ciao Luca ti basta andare in: Modifica Forum -> Icon Accetta solo gif,jpeg,jpg e png, io raccomando l'utilizzo di icone 32x32 per non rischiare di rendere il tutto troppo fuori misura... Alcuni siti per icone: https://www.flaticon.com/ https://icons8.com/icons
  23. luca314

    Icone per forum

    Ciao, volevo sapere come si personalizza ogni icona che identifica i forum. Ho provato tempo fa seguendo la guida in inglese, ma non riuscendo ho lasciato perdere. Ora vedo che anche qui c'è questa modifica. Mi date qualche aiuto per la configurazione sulla versione 4? Grazie mille
  24. Askancy

    4.4.3 Beta 1 - Note di rilascio

    Core Aggiornato CKEditor alla 4.11.4. Aggiornato LinkedIn login handler con l'uso di LinkedIn v2 API. Prestazioni migliorante quando vengono uniti due commenti con reazioni di membri per siti di grandi dimensioni, Miglioramento delle prestazioni quando si lavora con lo storico delle modifiche Migliorata la sicurezza di come vengono gestite le password nel codice per ridurre le probabilità che una password venga inclusa nel log degli errori Migliorata la visualizzazione della pagina di conferma dell'aggiornamento. Migliorate le prestazioni del flusso di attività più recenti nei profili utente. Improved anonymous log in tracking to resolve an issue with "Since my last visit" activity streams Improved the UX configuring moderator permissions for clubs, including the ability to disable club-level moderators. Improved database error reporting in certain error situations. Improved performance of a 4.1.8 upgrader step. Fixed multiple formatting concerns with custom profile fields. Fixed an issue where restoring soft-deleted content would throw an exception under specific circumstances ( e.g. when there was no record in the soft deletion log ). Fixed an issue where the member group restriction to require one piece of approved content before users can bypass content moderation was not correctly applied to posts made before registering. Fixed an issue where deleting a member's content and then deleting the member may result in the content not being removed. Fixed SVG images breaking when served through the built in image proxy. Fixed an issue with profile completion if you choose not to upload a profile photo. Fixed third party processor information not showing when users are forced to reaccept an updated privacy policy. Fixed the "Remove followers from uncommented content" setting not working. Fixed an issue where clicking to delete a member twice might result in all status updates being removed from the search index. Fixed an issue where copying content from one area with an attached image and pasting into another area may result in a broken image. Fixed an issue where allowing a user to moderate comments, but not items, would result in an error when using the multi-moderation menu. Fixed inability to edit profile fields by members if the field was not displayed on the profile. Fixed invalid HTML in the quick search form. Fixed an issue where a comment or post made before registering which requires moderator approval after the registration is completed may not update the container flag to indicate that comments within the container require approval. Fixed an error where the member view in the AdminCP may become broken if the member history for the user includes an old subscription group change and Commerce is not installed. Fixed an issue where broken letter photos may be displayed in emails. Fixed an issue with clean up tasks where they may try to delete a member that doesn't exist. Fixed an error that can occur if you double click the "unfollow" button quickly. Fixed autosaved content in the editor not clearing out when it was deleted within the editor. Fixed an issue where MFA while the login would send 3 'new device' emails to the member instead of only one. Fixed an issue where attachment links inserted into content may have a hard coded URL. Fixed an upgrade issue where custom file storage configurations in 3.x may not be preserved correctly when upgrading to 4.x. Fixed an uncaught exception when visiting a specifically malformed follow link. Fixed attachment bbcode tags not converting correctly when upgrading from version 2.0 or older. Fixed the About Me default custom field not showing on new installs. Fixed email statistic charts so they report more accurately. Fixed issues with performing advanced member searches in the AdminCP when multi-select custom profile fields are present. Fixed a minor inconsistency with group name formatting. Fixed an issue where items and comments queued for deletion or submitted by a guest prior to registration are returned via the REST API. Fixed an error when searching a specific search string. Fixed a possible error that can occur during login when using the post before register feature. Fixed the Notification Settings form in the Admin CP so that it can save properly. Fixed an issue where Login Handlers were shown out of order. Fixed an issue where the canonical link HTML tag may include unnecessary query string parameters (i.e. filters). Fixed an issue where AdminCP settings search results were not always highlighted when clicked on. Fixed an issue where the pagination for comment and review areas wouldn't link directly to the comments area when Javascript is disabled. Fixed an issue where content item and comment widgets would show content from not specified categories. Fixed an issue where editor auto saved content may not be removed. Fixed an issue where some content may not show a report link. Removed the hide signatures toggles from guests when they are able to see signatures. Prevented search engine spiders from following the cookie notice dismissal link. Removed poll votes from showing in the All Activity stream. Removed ability to copy theme settings. Removed the unread indicator in several widgets because it can't be used there because of the widget cache. Removed the ability to toggle cover photos in clubs list when no image was uploaded. Fixed an issue where the support tool could incorrectly report undiagnosed problems. Fixed missing images when lazy loading is enabled in several areas. Fixed an HTML validation issue with mini-pagination next to multi-page content item titles. Fixed an uncaught exception which is thrown by the Admin Notification System. Fixed member validation display issue in ACP notifications page while mobile. Fixed attachments being added to an editor which has attachments disabled. Fixed an issue where a display name sync error may be displayed on the AdminCP member profile. Fixed two language strings where countries have changed their names: Macedonia is now North Macedonia and Swaziland is now Eswatini. Fixed some broken messenger related links. Core Clubs Fixed "Clubs" tab showing when splitting content even if clubs are disabled. Fixed display issue with club tabs on mobile devices Removed ability to reorder club tabs on mobile devices Forums Fixed a duplicated error code in the topics REST API endpoints. Fixed images used in forum rules not displaying when image lazy loading is enabled. Fixed a potential upgrade error when reformatting forum rules during the 4.0.0 upgrade routine. Commerce Added an additional subtotal language phrase to the cart summary for localization flexibility. Improved legacy parser to potentially allow conversions of tables in content. Changed renewal terms to not allow $0 renewals. Fixed an issue where a cancelled subscription may still generate a renewal invoice (and subsequently charge the user). Fixed an issue where up/downgrading a purchase could result in an error. Fixed tax class being lost with renewal terms in some cases. Fixed an issue where images may not show in printable invoices if lazyload is enabled. Fixed support stream date-based filters producing incorrect results. Fixed stock action text not defaulting in the form when creating a new ticket from the AdminCP if you do not use a signature. Fixed an issue where the password field on the store checkout form might disappear if using Chrome's password autofill feature. Fixed an issue where invoices may not have a billing address set when one is available. Fixed an issue where a template error may be thrown for non-recurring subscriptions. Fixed a missing language string if you had servers configured prior to upgrading to 4.4. Fixed adding a custom package to an invoice. Fixed an exception being logged when rebuilding the search index if any custom packages have been created. Fixed the PayPal Billing Agreements radio element not showing selected if BAs are enabled. Fixed an issue where files uploaded to a custom field may not be downloadable. Removed a stray HTML end tag. Restored Braintree gateway option. Included a disclaimer about qualification process. Pages Fixed an issue where cloning a custom field would result in a database error. Fixed an issue on the media page where the "File Overview" Tab was not set as activated and also not clickable when one or more files from the file list were selected. Added last modified date to database category and record sitemaps. Gallery Changed the reputation type flag for album comments and reviews to resolve bugs where the reputation may be mistakingly treated as if it belongs to an image comment or review. Fixed an issue submitting images to an album if the category requires moderator approval. Fixed an error that can occur when downloading the original image in Gallery if the original image is missing on disk by forcing the largest available size to download instead. Fixed image lazy loading not working correctly in category rules, descriptions and custom error messages. Fixed the submission dialog box potentially showing an incorrect dialog title. Fixed an issue where uploaded videos could not be played in the lightbox. Fixed editor showing twice for each image during submission. Downloads Added a group setting that will allow users to bypass download restrictions when downloading a file that's been purchased. Added the ability to shut off version numbers per-category. Improved the header styling on the homepage. Improved performance, especially of the index page. Reduced top spacing (margin) of the sidebar when viewing the index page. Fixed an issue where custom fields may show out of order. Blog Fixed an issue where the previous and next link under the blog entry could link to hidden or soft deleted entries. Fixed some minor UI issues with the "Blogs" widget. Calendar Added an option to prevent edits and RSVPs for events that have passed. REST & OAuth Fixed the search REST API endpoint. Converters Improved vBulletin archive redirects. Improved vBulletin blog conversions to retain the date the blog or blog entry was followed. Fixed an issue where converted members won't be marked as completed. Fixed an issue when trying to convert from a platform with converters for apps that are not installed. Fixed an issue where PM replies may be duplicated when converting from vBulletin. Upgrader Fixed an edge case issue where some legacy customers may be unable to use the AdminCP upgrader. Changes affecting third-party developers and designers Backwards-incompatible changes that may affect third party applications / plugins: Methods that handle passwords in login handlers (`authenticateUsernamePassword()`, `authenticatePasswordForMember()`, `changePassword()`) now receive an object which can be cast to a string, rather than a normal string, for the password. This reduces the likelihood of a password being included in an error log. The `onPassChange` MemberSync callback now receives an object which can be cast to a string, rather than a normal string, for the password. This reduces the likelihood of a password being included in an error log. Enhancements / fixes for developers: Added a new constant `\IPS\DEV_LOG_HEADERS` which allows you to log all headers being sent during responses. Better abstracted code that dynamically builds class paths for areas that are no longer using iterators. Improved some extension skeleton files to not cause a ParseError once the extension is created. Fixed color fields not initializing for new rows added in a manageable matrix. Fixes that only affect developer mode or third party apps/plugins: Fixed some functions not being called from the root namespace and throwing warnings when in developer mode. Fixed an undefined index loading form to add a new hosting server in Commerce. Code-level fixes that may have been causing bugs in third party apps/plugins: Added code comments to all of the default constant values in init.php explaining what they all do. Ensured all default wizard instances are cast as a string before being sent to the output handler. Fixed an issue when pluralization and sprintf functionality is used together and the placeholder is used in the pluralized string. Fixed an issue with post before register where it was assumed content items would have a container. Fixed an exception when post before registering is checked against a content item that supports reviews but not comments. Fixed some ambiguous column concerns with the `\IPS\Content\Item::_comments()` method. Fixed an issue editing titles via Ajax when the item class does not use containers. Fixed an issue where the release date may not show correctly for third party plugins or themes. Fixed some functions not being called from the root namespace and throwing an IN_DEV warning. Fixed the widget configuration form being called twice which may result in some form elements duplicating. Improved some extension skeleton files to not cause a ParseError once the extension is created. Traduzione della notizia in corso.
  25. Gianluca73

    Immagine nei blocchi

    in che senso? intendi inserire un blocco html nel quale poi mettere il src image? c'è un plugin per mettere un blocco html? grazie
  26. Askancy

    Vendo licenza IPB a 90€

    Ciao, mi dispiace ma la licenza è già stata venduta...
  27. stan

    cerco licenza IPB

    ciao a tutti cerco licenza di IPS, se qualcuno la vende che mi contatti
  1. Load more activity
×
×
  • Crea Nuovo...

Important Information

By using this site, you agree to our Terms of Use.