Download version 2.0.0 (…at last)

This version should be stable and error free.

I added a “Theme options” page for customization without need of editing CSS or php.
You can download here phT2_0_1.

Please, report any problems living a comment. If no major issues are reported I will upload the theme to WP Themes repository.

Thanks for all your previous comments and support.

11 Responses to “Download version 2.0.0 (…at last)”

  1. Phogulum Says:

    Still gives me same error as before:
    Warning: Cannot modify header information - headers already sent by (output started at /wp-content/themes/phT2/index.php:1) in /wp-content/themes/phT2/get_resolution.php on line 10

  2. Fran Simó Says:

    I just uploaded the 2_0_1 version. I hope this fixed…

  3. Ben Says:

    I have the same problem as Phogulum

  4. Jonathan Mandel Says:

    Unable to change favicon. I’ve uploaded a new favicon to

    http://blog.checkerbox.com/favicon.ico

    and set the Favicon option on the phT theme options page to point there. But the default favicon still shows up.

    What am I doing wrong here? Thanks.

  5. Fran Simó Says:

    Jonathan: you should upload to the plugin directory /wp-content/themes/phT

  6. dawn Says:

    I have the same error as Photoglum. I have downloaded and installed the new 2.01 version. You can see the error at http://darmfield.com/photos.

    Thank you.

  7. dawn Says:

    I am getting the same error that Phogulum was getting. I have installed version 2_0_1, and still get it. You can see the error on my website at http://darmfield.com/photos. Can you please advise?

    Thanks so much.

  8. allan Says:

    I’m getting the same error as Photoglum. Any fix yet?

  9. Mark Says:

    Do you have version 2.0 I can download? I am getting the same error as Photoglum but would like to use this theme. I can edit the stylesheet myself if need be.

  10. Fran Simó Says:

    I don’t get the error on my servers so I need help… I’m working to fix it with allan… as soon as I can fix it I’ll send you an email 2.0 had the same error.

  11. Mark Says:

    Is it a problem with the cookie? If so, can the cookie be removed?

Leave a Reply