Tickets :: [#9346] Cachejs doesn't work for javascript files moved to Core

6.0.0-beta1

7/30/25

Summary	Cachejs doesn't work for javascript files moved to Core
Queue	Horde Framework Packages
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	goncalo.queiros (at) portugalmail (dot) net
Created	10/27/2010 (5390 days ago)
Due
Updated	10/29/2010 (5388 days ago)
Assigned
Resolved	10/28/2010 (5389 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/29/2010 02:41:08 PM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #5	Reply to this comment
[Show Quoted Text - 10 lines][Hide Quoted Text] I can't reproduce - I use cachejs and everything works fine for me. The Role package was created by me approximately two months ago (along with the movement of the javascript files into framework libraries). If you have not run the horde/Role post-installation script since August, then Horde will not be installed correctly. Various other devs have been tweaking installation/PEAR related features the last few weeks so maybe something they have done has caused your problem to manifest itself. My fault (sorry Michael), i had the registry equal to the .dist, which is incorrect, since the fileroot should be a full path.

10/28/2010 10:31:48 PM	Michael Slusarz	Comment #4	Reply to this comment
Michael, im developing on Horde for more than a year now, always using the install_dev script..did this changed? Because some days ago, everything was working fine (and it still is) only running this script. The only problem is really the javascript files that were moved to framework, that are not found when cachejs conf is activated..If the conf is not active, the files will be normally included on the page. I can't reproduce - I use cachejs and everything works fine for me. The Role package was created by me approximately two months ago (along with the movement of the javascript files into framework libraries). If you have not run the horde/Role post-installation script since August, then Horde will not be installed correctly. Various other devs have been tweaking installation/PEAR related features the last few weeks so maybe something they have done has caused your problem to manifest itself.

10/28/2010 08:12:34 PM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #3	Reply to this comment
You need to correctly install Horde - you can't run Horde directly from a snapshot or git checkout. See http://www.horde.org/source/git.php javascript libraries are installed via PEAR (you must correctly configure the horde/Role package) Michael, im developing on Horde for more than a year now, always using the install_dev script..did this changed? Because some days ago, everything was working fine (and it still is) only running this script. The only problem is really the javascript files that were moved to framework, that are not found when cachejs conf is activated..If the conf is not active, the files will be normally included on the page.

10/28/2010 06:45:42 PM	Michael Slusarz	Comment #2 State ⇒ Not A Bug	Reply to this comment
You need to correctly install Horde - you can't run Horde directly from a snapshot or git checkout. See http://www.horde.org/source/git.php javascript libraries are installed via PEAR (you must correctly configure the horde/Role package)

10/27/2010 03:55:06 PM	goncalo (dot) queiros (at) portugalmail (dot) net	Comment #1 Priority ⇒ 1. Low Patch ⇒ No Milestone ⇒ Queue ⇒ Horde Framework Packages Summary ⇒ Cachejs doesn't work for javascript files moved to Core Type ⇒ Bug State ⇒ Unconfirmed	Reply to this comment
If we activate cachejs conf, the recently javascript files that were moved to core will not be included in the page, since the call to filemtime will look for those files on their previous location (inside horde/js)