Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade 1.7 to 1.8 Error 404 /activity... index.php forward command (Trac #3900) #3900

Closed
elgg-gitbot opened this Issue Feb 16, 2013 · 3 comments

Comments

Projects
None yet
1 participant
@elgg-gitbot
Copy link

elgg-gitbot commented Feb 16, 2013

Original ticket http://trac.elgg.org/ticket/3900 on 41746149-07-27 by trac user stevet123, assigned to unknown.

Elgg version: 1.7

I'm upgrading to 1.8 from 1.7
I enter the url .../upgrade.php & all works
HOWEVER, index.php is called... in this code forward('activity') is called
I get a 404 error because 'activity' does not exist.
There's no directory/subdirectory for 'activity'.
If I remark out the forward('activity') command my site comes up (but not in a clean manner).

What am I doing wrong... how can I get past or correct?
Thanks!

Steve

@elgg-gitbot

This comment has been minimized.

Copy link
Author

elgg-gitbot commented Feb 16, 2013

cash wrote on 41746165-06-24

The upgrade instructions say to update your .htaccess file with the new rewrite rules. If you never changed your .htaccess, you can just copy htaccess_dist over it.

@elgg-gitbot

This comment has been minimized.

Copy link
Author

elgg-gitbot commented Feb 16, 2013

trac user stevet123 wrote on 41747569-04-16

I have copied over htaccess_dist over to .htaccess & made rewrite rule updates according to my configuration. It appears I'm having an issue with /pg/... where is this set?

I can enter url with wwwroot/FA/pg/activity and will get a reply (non-formatted, but works)... system is trying wwwroot/FA/activity and THIS DOES NOT work

@elgg-gitbot

This comment has been minimized.

Copy link
Author

elgg-gitbot commented Feb 16, 2013

cash wrote on 41748132-09-18

This is not a bug with Elgg as far as I can tell, but a problem with your install. As this is a bug tracker, this is not the correct place to get help with this. Please seek assistance at the Elgg community site at http://community.elgg.org/. If it is later determined to be a bug, come back and reopen. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.