WordPress.org

Make WordPress Core

Opened 23 months ago

Closed 23 months ago

Last modified 23 months ago

#20932 closed defect (bug) (invalid)

WordPress 3.4 RC3 - Theme module very slugglish!!!

Reported by: belantos Owned by:
Milestone: Priority: normal
Severity: major Version: 3.4
Component: General Keywords:
Focuses: Cc:

Description

WP 3.4 will be very snappy. It is a shame that this is not true of the theme module that is still extremely sluggish for no reason. I think it should be optimised before the final release.

Since all other modules are extremely fast (very well done!!!), it is a shame the theme module is so slow. For this reason I set it as a major issue.

Change History (13)

comment:1 follow-up: helenyhou23 months ago

  • Keywords theme module performance removed

Could you clarify a bit as to what you mean by the theme module? Perhaps steps to access it and which bits are sluggish?

comment:2 helenyhou23 months ago

  • Keywords reporter-feedback added

comment:3 in reply to: ↑ 1 belantos23 months ago

Replying to helenyhou:

Could you clarify a bit as to what you mean by the theme module? Perhaps steps to access it and which bits are sluggish?

In the admin area I can click on Posts, Media, Pages, etc, they all load in an instant, however, when I click on Appearance it takes a very long time to load.

It is in reality the Themes link that load very slowly.

comment:4 belantos23 months ago

  • Keywords reporter-feedback removed

comment:5 follow-up: nacin23 months ago

How many themes do you have installed?

comment:6 in reply to: ↑ 5 belantos23 months ago

Replying to nacin:

How many themes do you have installed?

Only one, EvoLve.

comment:7 follow-up: nacin23 months ago

Okay. This is related to #20933. On each themes.php hit, we run an update check. Clearly, yours are broken. So it is trying to make an HTTP request that ends up timing out. Thus, the page is super-slow.

We don't currently cache API failures. I think we probably should temporarily do so, for themes.php. Perhaps something we can do in 3.5.

comment:8 in reply to: ↑ 7 belantos23 months ago

Replying to nacin:

Okay. This is related to #20933. On each themes.php hit, we run an update check. Clearly, yours are broken. So it is trying to make an HTTP request that ends up timing out. Thus, the page is super-slow.

We don't currently cache API failures. I think we probably should temporarily do so, for themes.php. Perhaps something we can do in 3.5.

How can my installation be broken? I had 3.4RC2 and I upgraded it to RC3 this morning.

comment:9 follow-up: nacin23 months ago

It's either your install or your server. Re-install 3.4-RC4. If it doesn't work, temporarily re-install 3.3.2. If it doesn't work, it's your server.

comment:10 in reply to: ↑ 9 belantos23 months ago

Replying to nacin:

It's either your install or your server. Re-install 3.4-RC4. If it doesn't work, temporarily re-install 3.3.2. If it doesn't work, it's your server.

I also have 3.3.2 installed and it works fine. Is RC4 available? I have only seen RC3.

comment:11 belantos23 months ago

OK, what I did was I ran the upgrade to the latest nightly build a few times. I then cleared the browser's cache and cookies. Now the Themes section seems to load a lot faster. The upgrade process may have had a glitch...

comment:12 follow-up: nacin23 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

The upgrade process may have had a glitch...

Sounds like it, yep. Thank you for taking the time to investigate this. I imagine #20933 is also solved for you.

comment:13 in reply to: ↑ 12 belantos23 months ago

Replying to nacin:

The upgrade process may have had a glitch...

Sounds like it, yep. Thank you for taking the time to investigate this. I imagine #20933 is also solved for you.

Yes, both tickets can be closed. Thank you for all the help.

Last edited 23 months ago by belantos (previous) (diff)
Note: See TracTickets for help on using tickets.