Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • That’s just the lite version. It really isn’t helpful in deciding on whether to buy the plugin at all.

    I’m interested in the wiki functionality and I can’t test this at all with this plugin.

    Is there no useful demo site or proper demo plugin somewhere?

    Goal difference bonus : “Only awarded in matches with a winning team and only on top of toto points”, according to the plugin, but this is not what I’m seeing. I’m seeing it added to the full score as well.

    I now see that the goal bonus is added to the full & toto score…which to me makes no sense at all.

    I’m guessing it’s not easy to change this logic?
    Ideally I’d like goal diffence to only apply to toto (not full) and the goal bonus would only apply when you have neither full or toto (so people still get some points).

    The issue appears to be with the goal difference and goal bonus – these appear to be added to the full score as well as the toto score

    I have a question on this too. I just entered the scores for my pool and have found that the scores people have been assigned don’t make sense.
    I put in 4 for full score, 2 for toto and 1 each for goal difference and goal bonus. Users who predicted 3-1 have got 6 points! Which suggests some peculiar additions going on.

    Surely if someone gets the full score they shouldn’t also get the toto score?

    Thread Starter dcollis

    (@dcollis)

    Ok, that’s great. I’ll give it a try at some point (I don’t actually have either IE7 or 8 myself – but it’s on all the work computers where I’m running the pool. Only devs where I work get to use other browsers unfortunately.)
    Thanks for the help as always!

    Thread Starter dcollis

    (@dcollis)

    If I edit out the fancy box line in pool.js, the JS error goes away.

    It looks to me like I don’t really need the fancy box code unless I’m worried about the stats page. Is that right?

    Thread Starter dcollis

    (@dcollis)

    It would appear that is actually the fancy box code that is the culprit.

    When I commented out the include_js/css lines for this in class-football-pool.php, the site started to work again.

    Basically this JS code appears to grind IE 8 & 7 to a halt on every page refresh, so it must be doing some heavy processing each time.

    What is this actually used for? Does it matter that I have commented it out? I get a JS error on the page now it’s gone. Will this cause me any issues?

    Thread Starter dcollis

    (@dcollis)

    Ah, nicely done.

    If I update, will it just overwrite code files or will it re-install the database & site pages too?

    Thread Starter dcollis

    (@dcollis)

    Thanks for the help, much appreciated.

    Hmm, joker/wildcard. Difficult to say which is best. Perhaps just bonus card is better…

    Thread Starter dcollis

    (@dcollis)

    I meant the text for the menu items that get created when the plugin is activated. But no worries, I translated these manually.

    Don’t worry about translating the entire of the help file. I managed to work most of it out thanks to Google. I am still a little confused about how the joker/wildcard works however (this part didn’t translate well at all). Can it be re-set after every game or only before the tournament? How exactly does it affect the points/scores?

    A quick question about the bonus questions feature:
    If say, you added a question “Which player will receive the golden boot?”. Can any of these be worked out automatically? Or will it always required the admin to go and mark the answers?

    Thread Starter dcollis

    (@dcollis)

    By the way, not sure if you’d be interested in adding this feature, but a similar pool to this that I’ve seen in the past allowed you to put the time that the first goal was scored in for each match (for extra bonus points). Obviously I could create bonus questions for each game to do this, but I thought it would be nicer to have it as part of the normal match predictions part. Just an idea anyway.

    Your plugin seems really good so far – many thanks for all your hard work!

    Thread Starter dcollis

    (@dcollis)

    The language files needed to go in to the root of the plugins directory (which does seem wrong to me, but it worked) and I needed to add the line:

    load_plugin_textdomain(FOOTBALLPOOL_TEXT_DOMAIN);

    into the end of the define.php. Finally, I needed to define the language I wanted in the wp-config.php – e.g. define (‘WPLANG’, ‘en_GB’);

    Where do the menu item text get defined?
    Also, any chance you’d be willing to translate your instruction page for me (Google Translate is doing a terrible job).

    Thread Starter dcollis

    (@dcollis)

    I managed to get it to work using the instructions here: https://ryan.boren.me/2004/11/01/localizing-plugins-and-themes/

    There are just a few more strings that need translating as well as the data file and I hopefully will have it working in English.

    I’m looking forward to testing it properly!

    Thread Starter dcollis

    (@dcollis)

    Otto – In general I would agree, however, I have seen scripts that do target specific versions – i.e. it does a quick scan to check as many sites as possible to collect a list of potential targets, followed by then running the full script on those targets (because the script might take longer so its better to target it). So if taking the version number off even stops 1% of attacks, its probably worth it (taking into consideration the number of non-techie people who will be running wordpress and might not be on top of things like security).

    But in general of course security through obscurity is not an option. It just doesn’t work – and other security measures are far more important. So I do take your point that it is pretty much pointless.

    whooami – That might be true for WF but I could list you several top-tier investment banks who would be running a sharepoint site (or similar) somewhere publicly accessible which would have the version number available somewhere. Its just not something that they care about.

    Anyway, in summary. Theres nothing to stop you taking the version number off. It doesn’t gain you anything having it publicly visible, so why not take it off… even if all it does is prevent 0.0001% of attacks ??
    Just never for a minute think of it as a real security measure.

    Thread Starter dcollis

    (@dcollis)

    Yep, I agree – not worth worrying about that much, and now I know that the wordpress devs don’t care I won’t bother trying to persuade anyone here of course (I was never that passionate about it in the first place – I merely asked a question and stated my opinion).

    It still doesn’t change my personal opinion however – and I will still suggest that they credit wordpress. But it is just an opinion – I don’t care that much! I’m not about to start demonstrating in the streets about it ??

    As for the security through obscurity discussion, I am personally of the opinion that it is generally a waste of time (I work as an IT consultant/software engineer in various investment banks – where that argument would never hold up)…. however, in the case of php open-source apps, where so many scripted attacks are made against particular versions to exploit particular bugs I would say that any added security (even if by obscurity) is a good thing….. this doesn’t mean you can’t still credit the project though ??

    p.s. If you think gas prices suck, you should come visit England… (it would give you a much bigger reason to send complaints to the number10 site I assure you).

Viewing 15 replies - 1 through 15 (of 18 total)