Imported Fromfrom: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/aadbb2766c9aae55#
By default cron (/tools/cron.php script) does it's job silently without
sending any e-mail to anybody.
However if add a Scheduled Task that would, for example, send out latest
added links on a website, then you'll notice soon enough that there are
several problems in these links: -
- links look like http://localhost/ (fixed
...
- in
...
)Jira Legacy server In-Portal Issue Tracker key INP-682
...
- links look like http://www.website.tld/tools/index.html (fixed in
...
)Jira Legacy server In-Portal Issue Tracker key INP-812
...
- links look like http://www.website.tld/admin/tools/cron.php?env=....
...
- (when mod-rewrite is enabled)
This all is happening because of ADMIN constant being defined in cron.php
script. Maybe it's defined to skip most of front-end specific code, which
also includes mod-rewrite link building.
I'm proposing to remove this constant now and in code, that really isn't
needed when cron is executed from PHP CLI place if with check for CRON
constant it defined all the time.
Task: wrong_links_build_from_cron.patch
Related Tasks
| Jira Legacy | ||||
|---|---|---|---|---|
|
Ready for testing.
--
Best Regards,
http://www.in-portal.com
http://www.alex-time.com