We have moved to Github. Please open tickets there.

Opened 17 months ago

Closed 17 months ago

Last modified 16 months ago

#4253 closed Defect (fixed)

problem with link after update from Elgg 1.7 to Elgg 1.8

Reported by: RCerceau Owned by:
Priority: normal Milestone: Elgg 1.8.3
Component: Blog Version: 1.8.1
Severity: minor Keywords:
Cc: brett@… Difficulty: trivial

Description



I´m trying to manage a problem with the link heritage from Elgg 1.7 in the new install (Elgg 1.8).

The migration from Elgg 1.7 to Elgg 1.8 brought a updating at VIEW.

In the past, some users had the pattern to copy the links in "elgg 1.7 format' inside the posts.

As you can supposed it is not working in the new version!!!!

The problem is to revert all the calls from OLD to NEW style.

An example:

old link: (Elgg 1.7)
  http://<SITE-URL>/pg/blog/read/<blog-number>/<blog-name>

new link:(Elgg 1.8)
  http://<SITE-URL>/blog/view/<blog-number>/<blog-name>

Put a 'RewriteRule' rule on the archive '.htaccess' could solve it. That´s the best choice?

see:
http://community.elgg.org/pg/forum/topic/831808/how-to-manage-link-after-update-from-elgg-17-to-elgg-18-/

By EVAN
The problem is probably not with /pg/, it's with "read" vs "view". You should submit this as a bug since we should definitely be maintaining backwards compatibility of urls.


Change History (3)

comment:1 Changed 17 months ago by cash

  • Component changed from Core to Blog
  • Difficulty set to trivial
  • Milestone changed from Needs Review to Elgg 1.8.3
  • Severity changed from major to minor

confirmed

comment:2 Changed 17 months ago by Cash Costello

  • Resolution set to fixed
  • Status changed from new to closed

Fixes #4253 added backward compatibility for blog read url

Changeset: ccd4b6e48010cfc62c2ee6c942836c1ab9c9c7fd

comment:3 Changed 16 months ago by Cash Costello

Fixes #4253 added backward compatibility for blog read url

Changeset: ccd4b6e48010cfc62c2ee6c942836c1ab9c9c7fd

Note: See TracTickets for help on using tickets.