Make WordPress Core

Opened 16 years ago

Closed 15 years ago

#11187 closed defect (bug) (worksforme)

Directory references - referrers gone in 2.9

Reported by: glenda's profile glenda Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.9
Component: General Keywords: referrers, home, directory
Focuses: Cc:

Description

I have WP running off a different directory and all the relative URLs are now broken:

On the front end:

  • agendacide.com - a page controlled from within WP
  • agendacide.com/minutes - runs WordPress and its own index page

All resulting references after updating from 2.9 core results in:
http://www.agendacide.com/wp-admin/upgrade.php?_wp_http_referer=%2Fminutes%2Fwp-admin%2F

Which returns a 404.

Impossible to log in or upgrade, all CSS broken.

Attachments (3)

WordPress › Upgrade.jpg (65.8 KB) - added by glenda 16 years ago.
Upgrade page resides at different URL
Agendacide › Log In.jpg (61.0 KB) - added by glenda 16 years ago.
Log in page results in different directory
General Settings ‹ Agendacide — WordPress.jpg (81.6 KB) - added by glenda 16 years ago.
General Settings

Download all attachments as: .zip

Change History (5)

@glenda
16 years ago

Upgrade page resides at different URL

@glenda
16 years ago

Log in page results in different directory

#1 @glenda
16 years ago

This referrer issue seems to be an issue only when initially trying to find the blog directory folder, initially.

Upon login, and adjustment, all is fixed, but initial login process is difficult still. this may be the only associated issue. Check the initial login process and their referrers... that seems to be the only problem.

#2 @scribu
15 years ago

  • Milestone Unassigned deleted
  • Resolution set to worksforme
  • Status changed from new to closed

Instead of having wp in the /minutes/ directory, you should do this:

  1. Create a 'Home' page and a 'Minutes' page
  2. Go to Settings -> Reading:
  3. Set "Front page displays:" [A static page]

By the way, try asking in the support forums before opening a ticket here.

Note: See TracTickets for help on using tickets.