3 May Operation Hacked By Stokw – 3HiLaLL – x1x1pezo1x1x and Takisik – TheNoBody

Hacked by Turkhackteam 3 May Operation Hacked By Stokw – 3HiLaLL – x1x1pezo1x1x and Takisik – TheNoBody www.turkhackteam.org

13 June 2009 | FireStats | Comments

7 Responses to “3 May Operation Hacked By Stokw – 3HiLaLL – x1x1pezo1x1x and Takisik – TheNoBody”

  1. 1 מחשבות, מחשבים, ושאר דברי בלע » Blog Archive » חור אבטחה בפיירסטטס 1.6.1 Canada WordPress 2.8.1 13 June 2009 @ 2:36 pm

    […] עוד פרטים פה. […]

  2. 2 dictionary Israel Windows XP Mozilla Firefox 3.0.10 15 June 2009 @ 1:01 am

    “server have to be improperly” – should be has, or servers.

  3. 3 omry Israel Debian GNU/Linux Mozilla Firefox 3.0.9 15 June 2009 @ 1:19 am


  4. 4 Suggestion United States Windows XP Mozilla Firefox 3.0.11 18 June 2009 @ 12:38 am

    I am sorry for the bogus name, etc. I wanted to make a suggestion for a future version of firestats. My suggestion is to add some code that uses the IP on the statistics page under the hits table and cross references that with the comments IP addresses and inserts the name of the commenter for the IP. That way if you have people who are frequent visitors you can easily see who they are from their comment name instead of just the IP. I waste a lot of time looking at the comments page trying to figure out who the IPs belong to.
    Thanks from a big fan of firestats! Keep up the great work!

  5. 5 JJP United Kingdom Mac OS X Safari 531.9 13 September 2009 @ 6:22 am

    Thanks so much for a GREAT plugin!

    I searched the F.A.Q’s for documentation and scoured some of your blog postings but I didn’t see anything reported on it so hence this request: to be able format the placement of the browser/OS icons hooked to the comment_author_link() function.

    It’s not “mission critical” but sometimes being able to control the exact placement of those icons within the comments area would be desirable with some theme designs as oppose to it ALWAYS being just to the right of the author’s name as it currently displays now. I’m thinking of it as an option setting within FireStats where the WP admin chooses between a Defaultstate (as it functions already) or a Custom state where the theme designer can place a piece of pre-defined code snippet within their comments loop structure where they wish to display the icons, for example: maybe before the comment author’s name, below it’s name or even below the Gravatar.

    If that’s not feasible no worries, it’s still an awesome plugin and I enjoy using it very much, thanks!


  6. 6 Ducky Sweden Windows Vista Google Chrome 6.0.472.55 15 September 2010 @ 7:35 am


    I’ve tried to install Firestats latest version. but I cant activate it.. Why? I get a really messy code on my screen..

    “Error installing FireStats tables: Databasfel: CREATE command denied to user ‘wrdprs2@p340’@’’ for table ‘missducky__firestats_hits’

    MySQL Version: 5.0.41-log
    SQL Query:
    CREATE TABLE IF NOT EXISTS missducky__firestats_hits ( `id` INTEGER AUTO_INCREMENT COMMENT ‘Primary key’, `ip_int1` BIGINT UNSIGNED NULL COMMENT ‘IP Address left 64bit’, `ip_int2` BIGINT UNSIGNED NULL COMMENT ‘IP Address right 64bit’, `timestamp` DATETIME NOT NULL COMMENT ‘Hit timestamp’, `url_id` INTEGER COMMENT ‘Hit URL ID’, `url_site_id` INTEGER NULL COMMENT ‘Site ID of url’, `referer_id` INTEGER COMMENT ‘Referer URL id’, `useragent_id` INTEGER COMMENT ‘UserAgent ID’, `session_id` VARCHAR(30) COMMENT ‘Client session ID’, `country_code` INT(4) default NULL COMMENT ‘Country code of IP address or NULL if unknown’, `excluded_by_user` TINYINT(1) DEFAULT 0 COMMENT ‘1 if user explicitly excluded record, 0 otherwise’, `excluded_ip` TINYINT(1) DEFAULT 0 COMMENT ‘1 if the ip is in the excluded ips table, 0 otherwise’, PRIMARY KEY (`id`), KEY `url_site_id` (`url_site_id`) ) COMMENT ‘Hits table’ ENGINE=InnoDB”

    That’s what I get.. Whats wrong??

  7. 7 omry Israel Linux Mozilla Firefox 3.5.8 18 October 2010 @ 12:23 am

    contact your administrator and tell him your mysql user is not permitted to create tables.







FireStats - the blog