For the record, I tried adding/substituting "*" with or in place of "params", and I tried substituting it with "title", all results just errored or said "You have to choose at least one column to display",
However, using some common sense, I went back to the myprefix_modules table, hit the "ordering" column to sort by, this showed "x-logged in-pop all" as value "1" above the "Logged in-private" (also value 1), So I clicked in the order column for the first, entered "2" and hit return. The CB Login page's module has now finally changed as expected.
I assume it's safe to change the ordering values like I did to whatever I want with values from 0 to anything higher, so I can for instance renumber all six of the login modules as desired to get them into my chosen order of preference? (e.g. I may want current number 5 order to be order 1 (or 0)
Well, I learnt something new today. Still a surprise to find these issues especially with the unpublished module. Can't say I've noticed it mentioned anywhere ever before, and it was only during some prolonged testing and an accidental discovery that I finally fathomed what might be going wrong.
BTW, I wonder why having "none" or some other unavailable position name (e.g. "DefaultCBLoginPage") in the value for the module's position would not be a more suitable and intuitive way of defining which is used instead of using an unpublished module in database order? It might then avoid all this confusion of not knowing which one is going to get selected (i.e. not based on position and ordering in backend module view).
As things stand, it almost feels like publishing something that is marked as unpublished is a sin against all common sense and security.
For the record, I tried adding/substituting "*" with or in place of "params", and I tried substituting it with "title", all results just errored or said "You have to choose at least one column to display",
The query would be as follows.
Code:
SELECT * FROM #__modules WHERE module = 'mod_cblogin' ORDER BY ordering
I assume it's safe to change the ordering values like I did to whatever I want with values from 0 to anything higher, so I can for instance renumber all six of the login modules as desired to get them into my chosen order of preference? (e.g. I may want current number 5 order to be order 1 (or 0)
Yes.
BTW, I wonder why having "none" or some other unavailable position name (e.g. "DefaultCBLoginPage") in the value for the module's position would not be a more suitable and intuitive way of defining which is used instead of using an unpublished module in database order? It might then avoid all this confusion of not knowing which one is going to get selected (i.e. not based on position and ordering in backend module view).
Because this module was created back in the Mambo days. Joomla didn't just start out as Joomla 3.0 or anything of the sort. CB runs on multiple versions of Joomla and long before all these nice features even exist. This was the only solution at that time. We however can not just suddenly change it as that's a usage change that has been in place for years. It'll be changed with CB 2.0 however as it'll be a migration and not an upgrade so we can depreciate out of date usages.
Kyle (Krileon) Community Builder Team Member Before posting on forums:
Read FAQ thoroughly
+
Read our Documentation
+
Search the forums CB links:
Documentation
-
Localization
-
CB Quickstart
-
CB Paid Subscriptions
-
Add-Ons
-
Forge
-- If you are a Professional, Developer, or CB Paid Subscriptions subscriber and have a support issue please always post in your respective support forums for best results!
-- If I've missed your support post with a delay of 3 days or greater and are a Professional, Developer, or CBSubs subscriber please
send me a private message
with your thread and will reply when possible!
-- Please note I am available Monday - Friday from 8:00 AM CST to 4:00 PM CST. I am away on weekends (Saturday and Sunday) and if I've missed your post on or before a weekend after business hours please wait for the next following business day (Monday) and will get to your issue as soon as possible, thank you.
-- My role here is to provide guidance and assistance. I cannot provide custom code for each custom requirement. Please do not inquire me about custom development.
SELECTÂ * FROM #__modules WHERE module = 'mod_cblogin' ORDER BY ordering
Yup, that's what I did several times the other day and again today (replacing # with my db prefix, plus removing one of the two underscores maybe specified by accident).
The query box adds in some tabbed spaces and whether I "Selected All" to clear them or not, the query errored saying I have to specify at least one column. Then for some strange reason it suddenly started working using the exact same copy and pasted full query (but only when clearing the query box's extra spaces.)
No idea why! maybe some odd spaces were left? But it works now.
krileon
