Closed (outdated)
Project:
Glossary
Version:
6.x-1.6
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Jan 2009 at 03:06 UTC
Updated:
1 May 2017 at 17:21 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
phpdiva commentedThe patch seems to be working fine for me.
I think you missed one spot (last line in this function should be also changed):
Sorry, no patch. Still trying to work out the patching on Windows (the different line endings mess everything up).
Also, a suggestion for glossary_path(). Either do this:
or perhaps define a constant in the beginning of the module file?
Comment #2
phpdiva commentedComment #3
Nick Urban commentedFearfox, thanks for the patch check.
I see that I missed that clearcache line. Fixed in this patch.
Regarding caching the results of variable_get, I do not think it is necessary. I looked at the source for variable_get and it does not make a database call; it merely reads from "global $conf", so the static variable seems redundant. Anything I'm missing there?
Comment #4
Nick Urban commentedOh, I forgot, I added a
</dd>on line 956 because the<dd>tags were not being closed. I meant to submit that as a separate patch but instead it is in the patch I just submitted.Comment #5
manoloka commentedHas this patch been added to the module?
It seem a good option (especially for other languages)
Any chance to port it?
Comment #6
POVYLAZZZ commentedsubscribing...
Comment #7
RAFA3L commentedsubscribing...
Comment #8
yochee commentedsubscribing too
Comment #9
cmstomsubscribed.
This patch didnt work, I got a hunk error.
I dont see the option inside the Site Config > Glossary to change the base path.
Comment #10
cmstomMy glossary.admin.inc.rej file includes:
Comment #11
cmstomI got the patch to work by using this patch command. I did get the message "Hunk #1 succeeded at 137 with fuzz 3" but the patch worked.
This is the command I used:
patch --ignore-whitespace -F3 < set_path2.patchHope this helps!
Comment #12
crispin commentedThe patch in 3 can no longer be applied to the current release
Just tried to update a site to v1.8 of glossary and I could not reapply the patch, we are working on a new one right now, will post it up here hopefully this afternoon...
Comment #13
nancydru