View Issue Details

IDProjectCategoryView StatusLast Update
0000213WackoWikiinstallerpublic2009-10-13 16:05
Reporterebal Assigned ToTann San  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status resolvedResolutionfixed 
Target Version5.0.betaFixed in Version5.0.beta 
Summary0000213: Improvements for the installer process
DescriptionSome notes/suggestions for the installer process.

01. In the first page, it could be nice when someone select a different
language to change the language settings, or it could reload the page
with the new language settings.

02. version-check
I would like to see a re-check button (reload page) when I fix the
permission on the folders.
And a note how to give the write perms:

chmod 0777 wakka.config.php _cache/ xml/ files/ files/perpage/ sitemap.xml

03. write-config

I strongly believe that DELETE setup directory isnt the right thing to
suggest. But rename it eg.

mv setup .setup

and a note for remove the write permission from wakka.config.php

eg. chmod 0664 wakka.config.php

Some not so important things:

04. database-install

When someone is trying to install the wacko database but there is not
any wacko database a nice message is appeared. But I would like to have
a recheck button because I can easly open my mysql database and create a
new wacko database. So I could click on recheck button to continue.

Of course there is a return button so I can go back and re-continue but
then I must click 2 buttons!!

05. database-install

when I reload the step database-install there are a lot of messages that
inform me about the tables existence.
But i'd like to have a check-box enable with DROP TABLES label and
enabled. If the checkbox is enable then
I quick sql statement

DROP TABLE `wacko_acls`,
`wacko_cache`,
`wacko_links`,
`wacko_pages`,
`wacko_pagewatches`,
`wacko_referrers`,
`wacko_revisions`,
`wacko_upload`,
`wacko_users` ;

could be sent to mysql and remove all the tables for re-insert (and
clean/fix) tables and data.
TagsNo tags attached.

Activities

administrator

2008-08-09 20:52

administrator   ~0000465

Tann San:
All very good points. I will implement all of these.

administrator

2008-08-09 21:00

administrator   ~0000466

we can split this in several issues...

ebal

2008-08-15 21:01

developer   ~0000472

When the wackowiki installation process isnt complete perhaps there should be a rewrite because the result is like this :

http://ebalaskas.gr/img/wackowiki.03.jpg

Tann San

2008-08-16 10:00

manager   ~0000473

I'm not sure how you got that to happen, it looks like the HTML has been broken.

ebal

2008-08-17 15:23

developer   ~0000474

I use lampp for all my projects (testing/development mostly),
i was trying to install a new wackowiki site (svn always) and i've typed a different url to see if i the installation process would break somehow.

ebal

2009-01-06 12:33

developer   ~0000551

in rev 219 i've fixed 01 (reload first page in selected language), seems to work

   foreach($lang_codes as $key => $value)
 {

        echo "\t<input type=\"radio\" id=\"lang_".$key."\" name=\"config[language]\" value=\"".$key."\"";

// Default or Selected Language

if ( isset ( $_POST["config"]["language"] ) ) {

    if ( $_POST["config"]["language"] == $key ) {

        echo " checked=\"checked\" ";

    }

} elseif ( $wakkaConfig["language"] == $key ) {

    echo " checked=\"checked\" ";

}

//

        echo " onClick=\"this.form.action='?installAction=lang'; submit(); \"";

        echo " class=\"input_lang\"><label for=\"lang_".$key."\" class=\"label_lang\">".$value." (".$key.")</label>
\n";

      }

pascalvmf

2009-01-06 13:59

developer   ~0000553

>I strongly believe that DELETE setup directory isnt the right thing to
>suggest. But rename it eg.

>mv setup .setup

humm I would suggest chmod 0 setup would be more secure

pascalvmf

2009-01-06 14:04

developer   ~0000554

>02. version-check
>I would like to see a re-check button (reload page) when I fix the
>permission on the folders.
>And a note how to give the write perms:

>chmod 0777 wakka.config.php _cache/ xml/ files/ files/perpage/ sitemap.xml

humm more secured would be :

during setup :

chown <wwwserver_user>.<wwwserver_group> wakka.config.php _cache/ xml/ files/ files/perpage/ sitemap.xml

chmod u+rwx,g+rwx,o= wakka.config.php _cache/ xml/ files/ files/perpage/ sitemap.xml


after setup :

chmod a-w wakka.config.php

ie: for debian apache server wwwserver_user = wwwserver_group = www-data

Tann San

2009-04-09 11:28

manager   ~0000618

01. Selecting a different language now reloads the page with the new language settings.

02. version-check now has retry buttons for when any of the areas fails. Details about how to set permissions are now given at the end of the installer.

03. write-config still recommends that users delete their setup directory. It allows an anonymous user to access the database as well as view already written config data. If the user needs the setup directory again then they can just unzip it from the relevant sourceforge back history of releases and re-upload it to their site.

04. database-install now has a retry button incase of a failure. I'm a bit unsure about this one since depending on the database issue more user action may be required such as manually deleting tables etc. Guess we'll have to wait for a case by case review.

05. database-install now has a "Delete Tables" option. If selected the user is prompted with a confirmation box when they try to progress to the database-install screen. On that screen the tables are removed and then a fresh install is performed.

Tann San

2009-04-09 11:33

manager   ~0000619

01. Selecting a different language now reloads the page with the new language settings.

02. version-check now has retry buttons for when any of the areas fails. Details about how to set permissions are now given at the end of the installer.

03. write-config still recommends that users delete their setup directory. It allows an anonymous user to access the database as well as view already written config data. If the user needs the setup directory again then they can just unzip it from the relevant sourceforge back history of releases and re-upload it to their site.

04. database-install now has a retry button incase of a failure. I'm a bit unsure about this one since depending on the database issue more user action may be required such as manually deleting tables etc. Guess we'll have to wait for a case by case review.

05. database-install now has a "Delete Tables" option. If selected the user is prompted with a confirmation box when they try to progress to the database-install screen. On that screen the tables are removed and then a fresh install is performed.

Issue History

Date Modified Username Field Change
2008-08-09 20:50 administrator New Issue
2008-08-09 20:50 administrator Status new => assigned
2008-08-09 20:50 administrator Assigned To => Tann San
2008-08-09 20:50 administrator Legacy => NEW
2008-08-09 20:50 administrator Reporter administrator => ebal
2008-08-09 20:52 administrator Note Added: 0000465
2008-08-09 21:00 administrator Note Added: 0000466
2008-08-15 21:01 ebal Note Added: 0000472
2008-08-16 10:00 Tann San Note Added: 0000473
2008-08-17 15:23 ebal Note Added: 0000474
2008-09-11 21:57 administrator Target Version 5.0.0 => 5.4.0
2009-01-06 12:33 ebal Note Added: 0000551
2009-01-06 13:59 pascalvmf Note Added: 0000553
2009-01-06 14:04 pascalvmf Note Added: 0000554
2009-04-09 11:28 Tann San Note Added: 0000618
2009-04-09 11:33 Tann San Note Added: 0000619
2009-04-09 11:33 Tann San Status assigned => resolved
2009-04-09 11:33 Tann San Fixed in Version => 5.4.0
2009-04-09 11:33 Tann San Resolution open => fixed
2009-04-11 01:54 Tann San Fixed in Version 5.4.0 => 5.0.0
2009-04-11 01:57 Tann San Target Version 5.4.0 => 5.0.0
2009-10-13 15:58 administrator Target Version 5.0.0 => 5.0.beta
2009-10-13 16:05 administrator Fixed in Version 5.0.0 => 5.0.beta
2010-03-08 10:14 administrator Category Installer => installer