in vechiul forum 2.0.17 aveai MOD-uri instalate ?oitza scrie:Salutare! Multumesc anticipat pentru ajutor
Am facut update de la 2.0.17 la 2.0.21, am copiat toate fisierele, am sters directorul de Install, am inlocuit viewforum.php cu o versiune mai noua (ca nu'mi apareau topicurile) iar acum am o problema cu posting.php (cred), in sensul ca nu pot da PostReply sau Quote - rezultatul fiind un blank cu header - am citit aici, am cautat sa rezolv cu solutiile de schimbare a codului din posting.php dar nu a mers! Alta solutie ar mai fi?
O zi placuta!
oitza roz
MOD'uri inseamna skin'uri? daca da, da! aveam si inca mai sunt, aceeasi problema si la eleAliniuz scrie:in vechiul forum 2.0.17 aveai MOD-uri instalate ?
Da. Cel vechi eraAliniuz scrie:deci n-ai mod-uri instalate... la viewforum.php ai facut back-ul ?
Cod: Selectaţi tot
$Id: viewforum.php,v 1.1 2005/02/28 18:20:02 acydburn Exp $Cod: Selectaţi tot
$Id: viewforum.php,v 1.139.2.12 2004/03/13 15:08:23 acydburn Exp $In afara de treaba aia cu MySQL blabla... si mi se sopteste in casca faptul ca aveam moduri!Upgrading from these versions is typically quite easy. First you should rename or copy your existing config.php to a temporary location. Next upload (see Installation for details if necessary) the new 2.0 files to the same location as your previous installation of phpBB 2.0, ie. overwrite the existing files. Next delete the newly uploaded copy of config.php and replace it with your existing copy (ie. rename or move back the copy you saved previously).
You should now run update_to_final.php which, depending on your previous version, will make a number of database changes. You may receive the occasional "FAILURE" during this procedure; they shouldn't be a cause for concern unless you see an actual "ERROR", in which case the script will stop.
MSSQL users, please note that during the update procedure, your existing forums table will be dropped and re-created. All data in standard fields will be retained. However, if you have modified the forums table and added additional fields or altered existing ones, these changes WILL be lost. If this is a significant issue for you, we advise that you comment out the "DROP FORUM TABLE" section in update_to_final.php, and instead manually alter the forum_id column to remove the IDENTITY setting (if it exists).
Once the update_to_final has completed, you MUST proceed to the Administration General Configuration panel and check all the values in General Configuration. This is essential if you were running any version before RC-3 since extra information needs to be entered to enable correct URLs to be outputted in emails.
2.4.3: Changes in language pack format
Please note that changes have been made to the format of both language and image localisations from previous RC's to RC-3. If you were running a version previous to RC-3 you WILL need to download new versions of all non-English language and localised subSilver images. You can delete any existing *_lang.gif files in the root subSilver/images directory since they were moved to subfolders in RC-3. In addition various changes to template variable names has occured from RC-2 through RC-4. It is highly unlikely that a template written for RC-2 will work without some changes in RC-4. Most of these changes are minor and can be found by examining the default subSilver template.
2.4.4: Upgrade from 2.0 Beta
Sorry but no direct upgrade is available from beta-1 (we did warn you!). If you are reasonably confident with the use of SQL, etc. you may be able to make the required changes to the database manually. You will need to examine the CVS check-ins to determine what and where changes are needed.
Utilizatori ce ce navighează pe acest forum: Niciun utilizator înregistrat și 1 vizitator