Updated to latest version and now when use get the error message below
"No path was selected to forward"
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | new-forward.patch | 1.41 KB | netsensei |
| #6 | forward-398806.patch | 3.83 KB | emackn |
| #2 | forward_change_path.patch | 991 bytes | jpsalter |
Comments
Comment #1
jpsalter commentedI just ran into this problem too. Changing the values $_GET['path'] to be $_GET['q'] solves the problem. I don't know what other implications this may have.
Comment #2
jpsalter commentedPatch attached. I've search and replaced all $_GET['path'] to $_GET['q']
Comment #3
jpsalter commentedOkay - the problem seems to be that the module has changed the way links are created (it builds its own): forward?path=node/xxx
This sheds some light on the problem.
http://drupal.org/node/320554
Sites that were using old versions of this module and building their own links (mine for example) will now be broken and need to change how the links are created.
Comment #4
paul conolly commentedWorks for me.
Comment #5
tirdadc commentedRegarding the patch in #2: you also need to change the following line in the forward_page() definition if you want the proper path to be forwarded in the email:
I just tested it, and it works fine now.
Comment #6
emackn commentedHere is a re-roll of both changes off the current dev branch
Comment #7
netsensei commentedWasn't really happy with the patch in #6. Contains debug code for one.
So here's a re-roll of the patch with these changes:
- changed regular expression
-
$_GET['path']to$_GET['q']Works for me.
Comment #8
seanrYou need to update how you're generating your links if you're not using the module's automatically generated links. This change was made deliberately because people wanted to forward non-node pages and there needed to be an easier way to handle the paths. The patches attached would revert to the old format and will actually break stuff. Try using Forward's own links or update your theme. Marking this as won't fix.