Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: Administration
    • Labels:
      None
    • Affected Branches:
      MOODLE_20_STABLE
    • Fixed Branches:
      MOODLE_20_STABLE
    • Rank:
      35894

      Description

      looks like I made a mistake somewhere, the last upgrade did not seem to reset the JS stuff

      TODO: evaluate on Tuesday and fix

        Activity

        Hide
        Petr Škoda added a comment -

        hopefully solved

        Show
        Petr Škoda added a comment - hopefully solved
        Hide
        Chris Collman added a comment -

        Hi Petr,
        For the 2.0t builds over the last couple of weeks, I use theme selector and only see a button that says "invalidate theme cache".

        I tried both IE and Firefox. on a windows local host. I did play with some themes but copied existing themes and renamed the folder.

        If you can not duplicate, I will build another localhost with a complete install package.

        Best Chris

        Show
        Chris Collman added a comment - Hi Petr, For the 2.0t builds over the last couple of weeks, I use theme selector and only see a button that says "invalidate theme cache". I tried both IE and Firefox. on a windows local host. I did play with some themes but copied existing themes and renamed the folder. If you can not duplicate, I will build another localhost with a complete install package. Best Chris
        Hide
        Petr Škoda added a comment -

        hmm, strange this works fine for me and others - the only problem is that people do not bump up version number after theme modifications sometimes. Also the themes are sometimes a bit borked during the upgrade. I do not understand what you are actually doing with the themes.

        Please try the theme forums first and then file a new bug with detailed steps to reproduce the problem if necessary.

        thanks

        Show
        Petr Škoda added a comment - hmm, strange this works fine for me and others - the only problem is that people do not bump up version number after theme modifications sometimes. Also the themes are sometimes a bit borked during the upgrade. I do not understand what you are actually doing with the themes. Please try the theme forums first and then file a new bug with detailed steps to reproduce the problem if necessary. thanks
        Hide
        Chris Collman added a comment -

        Hi Petr,
        I fired up a localhost I had here at work. Moodle 2.0 dev (Build: 20100331) last modified according to Windows explorer on 20100406. I see all the old themes with eraser marks on them. Plus Anomaly and Flower Power which I just downloaded. The button is still there at the top.

        I then followed Martin's announcement about Preview 2.0 to Moodle docs and clicked on the "get it" link. and installed that over my existing Moodle. Notifications still shows Moodle 2.0 dev (Build: 20100331) but it upgraded the blocks.

        On one of my home localhosts, I did not see any themes just the button and upgrading..

        I will delete the entire local host at home and put up another complete install package for 2.0. Sorry for the false error reporting. Agree that it is resolved until I break it again

        Show
        Chris Collman added a comment - Hi Petr, I fired up a localhost I had here at work. Moodle 2.0 dev (Build: 20100331) last modified according to Windows explorer on 20100406. I see all the old themes with eraser marks on them. Plus Anomaly and Flower Power which I just downloaded. The button is still there at the top. I then followed Martin's announcement about Preview 2.0 to Moodle docs and clicked on the "get it" link. and installed that over my existing Moodle. Notifications still shows Moodle 2.0 dev (Build: 20100331) but it upgraded the blocks. On one of my home localhosts, I did not see any themes just the button and upgrading.. I will delete the entire local host at home and put up another complete install package for 2.0. Sorry for the false error reporting. Agree that it is resolved until I break it again

          People

          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: