ocPortal Version 8 RC7 (bleeding-edge) - Comments
1 guests and 0 members have just viewed this: None
Control functions:

| To | × pt | For |
|---|---|---|
| temp1024 | 80 | Sup… |
| curtisbrew | 50 | Hel… |
| Fletch | 500 | Sup… |
| Fletch | 100 | The… |
| Duck | 200 | Pro… |
| Fletch | 100 | The… |
| Chris Graham | 100 | Hel… |
| Fletch | 100 | The… |
| Fletch | 100 | The… |
| Duck | 100 | Rea… |
The top 5 point holders for this week are…
Want points? Earn 350 when a member joins using a recommended address.
Also check out our community stars.
Points to spend? Buy a banner at the point store.
ocPortal Version 8 RC7 (bleeding-edge) by ocProducts
I have two hidden fields (both "Display in category-views catalog" and "Visible" unticked) that refuse to hide. One field, data type "10 random numbers and letters", shows up while editing an existing entry but not while entering a new entry. The other field, data type "a date", shows up while both adding and editing.
Could be others, I haven't checked.
It's not about hiding on edit forms, it is about hiding from display on the main site.
Auto-generated field types won't show on the add form.
Strange. Isn't the purpose of having hidden fields is to keep the person creating an entry from being able to manipulate the data?
Why would you want field XYZ hidden from someone while they are creating a new entry, but have it visible later when they decide to edit the entry. Doesn't that defeat the purpose of having hidden fields and the ability to collect virgin data from hidden fields?
Example #1… I use the data type "10 random numbers and letters" as a hidden field to create a random sort order to ensure no one can "stack the deck" to keep their catalog entry at the top of the list. Later the user goes back to edit their entry and the "hidden" field is no longer hidden and they are able enter all zero's into the field to put their catalog entry at the top of the list. No point it having it a "hidden" field at add time.
Example #2… I use a hidden field data type "Sequential number" to serialize the order in which catalog entries are created. This field is hidden at creation time, but set as visible on the list to a visitor. A user comes back later to edit their entry and changes the sequence number to try to manipulate when they created the entry.
What's the point of having hidden fields at entry time to collect data if the hidden field is exposed to manipulation at edit time? Right now, the only way to keep hidden collection data secure is to deny a user the ability to edit their entries (which could create other problems).
It was never intended to be to do with locking down data entry – it was to decide what is displayed to end-users. i.e. some data is for reference purposes rather than display purposes, or should only be shown on the full screen and not category screens.
Feel free to add your use cases to the tracker.
I actually have a list of different things I want done and I'll add them to the tracker when times comes and have you estimate a cost. Most are probably specific to my site and needs so I'll fully sponsor them, but make the mods available for others.
I would encourage adding stuff whether they'll be sponsored by you or not. The only caveats are to check it's not already there first, and that it's not overly specific (e.g. posting about some kind of gaming server front-end, or ebay affiliate system, that'd be out there – but stuff generally useful to broader audiences is good).
Have an idea not already in the tracker? Put it in yourself.
Bob
An error has occurred A symbol is missing: FB_CONNECT_LOGGED_OUT. This usually happens when Comcode is written without placing template/PHP code within a code tag. (version: 8-RC7, PHP version: 5.3.10, URL: /pg/start/index.php?keep_fatalistic=1&keep_safe_mode=1&redir
ected=1)
It appears that you are logged out from the public area but still logged into the members area. Strange …
Maybe I should check my FB application settings since the public and private keys are accurately reflected in the configuration.
Are your posts regarding RC6 or RC7? Just curious as I prepare to upgrade to RC7 and want to know if Facebook add-on is still a problem area.
Bob
When I accepted all the upgrader defaults and allowed it to check and 'fix' any files that needed it in the 'Theme upgrade', the upgrader made a change to my <personal theme>/global.css as shown below:
This was easy to spot because I have a quote box on my front page. Must go hunting for other arbitrary changes that took place …
I tried to reproduce this but couldn't, and there are no upgrade rules in that part of the file, so I think it must have been something else. That said, I did fix a couple of minor problems in the upgrader that I did find (happened when themes were upgraded more than once).
Bob
Bob
Now that you've said that, I remember reading it when adding the Activities addon. I hadn't been on the profile page much before the Activities addon so it didn't register that I had replaced the "posts" tab.
Thanks for helping out with my short-term memory loss!
Fix, please!
P.S. (added 29th April)
This is RC7, but I think it appeared in an earlier RC, possibly RC6 or even RC5.
Thanks, fixed.
I ask, because I still have the problem, and don't have a clue which 'script' is affecting this behaviour.
Yep!
Bob
Show 7 more replies