Closed (fixed)
Project:
Web Links
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Nov 2014 at 07:22 UTC
Updated:
23 Jan 2015 at 11:34 UTC
Jump to comment: Most recent
Abstract
After Activation of Weblinks module, it's not possible to flag the "Sticky to Top" option for nodes (the checkflag is not saved).
Description
Testing Enviroment
Comments
Comment #1
jonathan1055 commentedHi francescosciamanna,
Thank you very much for the detailed description and your testing results. I think this has already been discussed in #2030765: Editing a sticky node sets db field to -100 for non-weblinks nodes. Do not encode weight and remove the weight.inc file and #2148005: weblinks.weight.inc stores all contributions in sticky 100 and -100. Yes, there definitely is a problem and we'll try to find a good solution for you.
Jonathan
Comment #2
gstegemann commentedJonathan,
you're right. This issue is already known and was discussed in both mentioned issues.
@francescosciamanna: as a workaround I would suggest to install and enable the Weight Module which disables this behaviour.
Gerhard
Comment #3
francescosciamanna commented@GStegemann
Thank you for suggestion, the Weight Module seems can solve my problem. But imho even this Issue is the same of the twos mentioned by Jonathan, the latter are not so easy to be found, or at least is not so evident the link between the effect(this topic), and the cause(the two old topics). My intention was only make a small contribution to the community, mostly for these with poor/almost nothing coding knowledge like me, hoping that can save a little of time, if encounter a similar situation.
@Jonathan
Thank you all(including GStegemann) for your efforts on maintain this module, I really hope you can solve this issue not for me, since Weight Module does the job well, but for anyone else that can run into this issue in the future: we have 60 modules installed in our site and no need of Sticky option until we decided to open the Forum Section, fortunately I have personally some Troubleshoot experience that helped us to avoid one by one exclusion, in that scenario Weblinks is one of the last module to be tested and disabled in our test list both in installation-reverse-chronological and alphabetical order!
Cheers,
Francesco
Comment #4
jonathan1055 commentedHi Francesco,
Thank you for your report and careful testing. Sorry you had all that trouble.
On #2030765: Editing a sticky node sets db field to -100 for non-weblinks nodes. Do not encode weight and remove the weight.inc file I have made a patch to solve this problem. Is it possible for you to test it?
Jonathan
Comment #5
francescosciamanna commentedWith pleasure Jonathan, I'll test it within tomorrow (patch already downloaded). BR, Francesco
Comment #6
jonathan1055 commentedThank you. I have uploaded a newer patch file which also includes an update function to fix any bad values - see comment #14 in the other issue.
Comment #7
jonathan1055 commentedSetting this issue back to 'active', sorry it should not be 'needs review' as there is no patch here, only on #2030765: Editing a sticky node sets db field to -100 for non-weblinks nodes. Do not encode weight and remove the weight.inc file. Simpler if we keep just one issue to review.
Comment #8
jonathan1055 commentedFixed via #2030765: Editing a sticky node sets db field to -100 for non-weblinks nodes. Do not encode weight and remove the weight.inc file. See commit 5b1a7e4 for details.