Item Indexer / Search Tool / Shop Generator - php/sqlite3

that's how I use it...

This far it doesn't really prevent sql injections and stuff.... so protect it yourself or run it on your on local webserver :) haven't tried to run it in windows though :)

And make sure you have a SQLite version compiled with FTS (Fulltext Search).

Fixed the stack issue and also support the new login method. Get current script to get it working again for updates.

"

hyper_ch wrote:

And make sure you have a SQLite version compiled with FTS (Fulltext Search).

Is there a way to check for this, beside just to look if it works?

on *buntu I'd download the source:


apt-get source sqlite3


and then check in debian/rules for the configure options... but easiest is probably just to try.

tried to push it to a local xampp 'server' on windows, showed some issues... (maybe things that can/have to get configured by me?; some seem to be related to the script itself, maybe different behaviour?);

notices (just a bit annoying for their visibility in the 'main' window):
undefined index: action on line 35,undefined index: submit on line 36
(both shows up on top, the 2nd also in every action bar.

-Top also shows notices for "undefined constant PHP_SELF" on line 751 & 775
-Search also shows notices for "undefined variables" - leagueData & typeData (maybe just for uncomplete/missing files)

and finally: creating the Items-DB stops for "Maximum execution time of 30 seconds exceeded (on line 640) with a fatal error. Tried multiple times, to check if it can be done in partial steps, along with the information (at home) that it may need 3-4 minutes - but maybe its all related together and wont work...

"

Mr_Cee wrote:

notices (just a bit annoying for their visibility in the 'main' window):
undefined index: action on line 35,undefined index: submit on line 36
(both shows up on top, the 2nd also in every action bar.

That's your error_reporting in your php.ini. Just adjust it for not showing visible notices. Same goes for the rest.

You could try to add this to the beginning:

"

<?php

error_reporting(0); // Turn off all error reporting

"

Mr_Cee wrote:

and finally: creating the Items-DB stops for "Maximum execution time of 30 seconds exceeded (on line 640) with a fatal error. Tried multiple times, to check if it can be done in partial steps, along with the information (at home) that it may need 3-4 minutes - but maybe its all related together and wont work...

You'd also have to alter your php max run time. It seems yours is set at 30 seconds.

And this added to the top of the file

"

<?php

error_reporting(0); // Turn off all error reporting
set_time_limit(0);

"

hyper_ch wrote:

This far it doesn't really prevent sql injections...

Doesn't the prepare method prevent sql injections?

Not in the search yet. That's still one big sql statement without prepared replacement... being lazy there (needs to be fixed)

Thanks so far, following your hints solved the issues to make the db-indexing work... after this it still dont work properly (shows no entries in the selections for league and itemtype and of course - resulting? - no results); but I'll try to figure out if this is caused by my xampp prior to other actions.

Idea from your demo: would be nice to have a differentiation between unique and other items, either by a special mark or a varied colour for the item names. (if it can be detected easy enough)

well, you did add your username and password, right?

And you use the current version? There was a login update that now also has an additional hash...