DawPi

Wg mnie to Ty po prostu wpisujesz dane z tego drugiego logowania do ACP zamiast tego do swojego konta. Jak się możesz zalogować na forum i usunąłeś te dwa pliki z kropką na początku ( .htaccess i .htpasswd ) to musi się dać zalogować do ACP. Sprawdź dobrze. A jak nadal nie możesz to może na admin/ ustawiłeś fałszywy panel?

mieciu: zostanie to poprawione. Bo to oczywiście jest błędem i już pamiętam miejsce w kodzie by to poprawić.

Powinny. Tak, to muszę przetestować porządnie.

To nie chodzi o zmianę na nulleda tylko o fakt, że zmieniając forum z A na B forum A powinieneś skasować. Teraz rozumiesz? A czeka się tak jak to wynika z warunków licencji.

Right from the outset, I want to make it clear that I make no warranty or promises for the information in this post. I'm not an expert. It is merely an outline of the steps I have made to bring my server and IPB installation up to UTF-8 spec in the hope some other IPS customers will find it useful. Note also that this does *NOT* provide instructions to convert existing data in posts to UTF-8, however, any latin1 data already in your forum should work fine after making the changes listed below. I have not converted my existing data because I'm not too concerned that some old posts might have some scrambled foreign text, as long as the vast majority of latin1 still displays OK (as it does)... Conversion of existing data is a huge and dangerous task that most people won't need to do anyway, unless their primary board language is in a complex Asian script, like Japanese for example. About my decision to make the change: I'm am an IPB customer since the 2.0 days and my board was still in latin1. My board is primarily English language but it is based in Singapore and often addresses language queries from members, which are invariably in complex Asian scrips, primarily Thai, Japanese and Chinese, so I decided to make the switch to UTF-8 in order to guarantee everything functions correctly and future proof the database. Collation data was also missing from my database. More on that later... Only you can decide if you should make the change. If you're absolutely certain that your board will never have foreign languages posted, you're probably better off staying as you are... but I personally think that if you're board ever gets foreign scripts posted, it's prudent to make the change sooner rather than later as it will only get more painful the longer you leave it. There are lots and lots of UTF-8 flavours and obviously you choose the right one for your language. However, nearly everyone will be choosing 'UTF8_general_ci' or 'UTF8_unicode_ci'... What's the difference? Not much, but the latter had additional support for certain types of languages and although it is marginally slower, I chose UTF8_unicode_ci because of the complexity of the scripts sometimes posted on my forum. All of the instructions below reflect that, so adjust accordingly for your own installation. Some of the measures listed below will require you to have root access to your server, or a host that's willing to assist you make the changes (probably not going to happen). REMEMBER: BACKUP BACKUP BACKUP! So, now that's out of the way, lets look at what I did... ----------------------------- I think it important to get the native charset of your server set up accordingly. If you go to your ACP --> Support --> SQL System Vars you will see a list of various charsets running on your server. The ones you are most interested in are collation_server and character_set_server. Once you have set these, the others should inherit. In order to set these to UTF-8, open up your /etc/my.cnf file and add the following three lines under [mysqld]... collation_server=utf8_unicode_ci character_set_server=utf8 skip-character-set-client-handshake Save and restart SQL. Now you need to open up your php.ini file and ensure the following is in place... default_charset = "UTF-8" Save and restart Apache. So now we've got the server talkin' in in UTF-8 Now onto the database itself. If you're a legacy customer, your charset will almost certainly be latin1_swedish yadda yadda. You will have lines throughout your database that look like this... ) ENGINE=MyISAM AUTO_INCREMENT=2139 DEFAULT CHARSET=latin1; ... and are missing a 'collation' entry. There are a number of ways you can correct this, you could for example open up phpmyadmin and individually change each table/column/row but you'd be there all night. You could also automate it and so a search/replace via a terminal... in my case, I chose what I considered to be the safe way by downloading the database to my local machine, opened it up in a text editor and did a find/replace. After I'd finished, the above line now looks like this (for every instance (but DON'T touch the increment value, make sure your search/replace leaves that alone))... ) ENGINE=MyISAM AUTO_INCREMENT=2137 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci ; Save. Prepare to import the database back to your live board. The following is important (so that any tables created by IPB in the future are in UTF-8)... In your phpmyadmin, ensure that the MySQL connection collation is set to 'UTF8_unicode_ci'. Add the following line to your conf_global (or if it's there already, change it to UTF-8)... $INFO['sql_charset'] = 'utf8'; Now import your database and bring it online to your live board. Immediately, go to ACP --> System Settings --> Server Envoronment and set the Document Character Set to UTF-8 You're done... ไม่เป็นไร Wyświetl pełny artykuł

What is (DB23) Invitation System? It is a modification for IP.Board Forum in 2.3.x version,which enables registration on the forum after giving the correct invitation code. Accessibility: Administration Panel Ability to turn on / off the modification Ability to give invitatiOns to certain groups of users Ability tO give unlimited amount of invitations to certain groups of users Access to statistics: who invited most people, .... Ability to define invitation's validity Ability to definE account's validity after registration (before confirming) Ability to change the number of invitations for every user individually Ability to define allowed domains, on which users will send emails Ability to inform the user about received invitations and havig their y number through email / PM. PM is sent to user of ID 1 Ability to define in which gruops the new user should be after confirming the account by inviting person User's Panel Ability to send invitatios Invitatios valid throug x hours. After this time they lose their validity. The user who sends an invitation receives this invitation back After registration the user who sent the invitation has x days to confirm the invited person's account. After this time the account will be removed and the user will receive the invitation back. After accepting the user goes to the group which is defined by the administrator In the controll panel user sees how many invitations he has to use and if he was invited he sees also who invited him In the controll panel user has a list of all the users that he invited and also list of users who need to be confirmed In the user's profile view on the left there are information how many users he invited In the user's profile view on the left administrators see how many invitations user has In the profile view there is a tab, which shows last 10 users registered after inviting and accepting them Screens: Wyświetl pełny artykuł

Nie widzisz tego tematu, bo jest w dziale dla premium. Dla Twojej wiadomości - właściciel tego forum pracuje w IPS.

Jest modyfikacja. Prościej się nie da.

W celach testowych ( bo musisz to zrobić, ja z racji braku dziś czasu nie mogę ): Otwórz plik: admin/sources/classes/bbcode/core.php Znajdź: return "<img src='" . $this->settings['emoticons_url'] . "/{$_emoImage}' class='bbc_emoticon' alt='{$_emoCode}' />"; Zamień na: return "<img src='" . $this->settings['emoticons_url'] . "/{$_emoImage}' class='bbc_emoticon' alt='{$_emoCode}' title='{$_emoCode}' />";

Swoje zdanie wypowiem jak zrobię upgrade forum. Oczywiście najpierw na localhoście bo nie lubię niespodzianek.

Problem ROZWIĄZANY. Jeśli są jakiekolwiek wątpliwości, pytania proszę o założenie nowego tematu. Wszelkie uzasadnione reklamacje/pretensje/sugestie/rady przyjmuje ekipa forum.

Jak to wersji 3.x to tylko ten mod, dostępny w ramach usługi premium na tym forum: (T30) Pips & Team Icons 1.0.0.

Problem ROZWIĄZANY. Jeśli są jakiekolwiek wątpliwości, pytania proszę o założenie nowego tematu. Wszelkie uzasadnione reklamacje/pretensje/sugestie/rady przyjmuje ekipa forum.

Nie uważam tak.

Bo alt służy jak nie będzie grafiki, a Ty mówisz o "title".

No to polecam odinstalować ten stary, a zainstalować nowy - instrukcja na forum.

Problem ROZWIĄZANY. Jeśli są jakiekolwiek wątpliwości, pytania proszę o założenie nowego tematu. Wszelkie uzasadnione reklamacje/pretensje/sugestie/rady przyjmuje ekipa forum.

Popracuj nad reputacją na forum.

Witaj, hym, domyślnie kod emotek to: <img src='http://localhost/300/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=' ' /> Zmieniając teraz te kody można narazić się na wywalenie poprzednich postów, choć ponoć w IP.Board 3.x ma to być już niemożliwe. Mogę poszukać rozwiązania, ale na 99,99% trzeba będzie edytować kod forum - a od wersji 3.x nie lubię tego robić, chyba, że ktoś bardzo chce.....

Z tego, co ktoś zasugerował ( nikt z IPS ) chodzi o kontrolę legalności forum -> nie tego, na który zmieniasz, ale z któego. Co ticket powinien mieć? Może: "Hello, i want change domain name for my board. Please change this ASAP to: http://duzebalony.pl Thanks. "

Problem ROZWIĄZANY. Jeśli są jakiekolwiek wątpliwości, pytania proszę o założenie nowego tematu. Wszelkie uzasadnione reklamacje/pretensje/sugestie/rady przyjmuje ekipa forum.

W załączniku.

Default Avatar.

Dzisiejsi top użytkownicy to dodatek IPS-u dostępny w panelu admina w zakładce Manage Hooks. Od najnowszych postów masz to rozszerzenie: (SOS30) Latest Discussions v1.0.2.

Podałem dokładny link do postu Wareczka, gdzie podaje link do plików które trzeba nadpisać by problem z nopermission zniknął z IP.Shoutbox. Nie zgrywaj się bo pomyślę, że naprawdę tego nie zrozumiałeś.