I'm using lynx version 2.8.7rel1 on cygwin. When I try to change a drop down box, I get the following message when it is highlighted: "UNMODIFIABLE option list", and I cannot change its value from the default. How can this problem be fixed? Thanks!
This looks like a bug in lynx 2.8.7-1
It looks similar to this bug which was reported fixed in 2005:
fix: when first "option" element of "select" had "disabled" attribute, Lynx
turned the entire "option/choice list" UNMODIFIABLE. The "disabled"
attribute of later "option" elements within the same "select" did not have
this effect. If the "disabled" attribute is honored, it should disable only
that element, not parent element or sibling elements (report by Paavo
Hartikainen) -TD
You can work around this problem by reverting to lynx 2.8.5-4 instead of 2.8.7-1 (2.8.5-4 is still available in cygwin -- when you are in the "Select Packages" interface, click on the version number for lynx in the "New" column until that version appears).
Related
I am trying out VS2017 (previous using VS2015), and I'm trying to navigate my code using Ctrl+Right/Left. Instead of the typical behavior of moving to the next or previous word, it changes the focus to different UI elements.
Using Ctrl+Arrows I can get to the reference counts from CodeLens, quick actions, and the project and item dropdowns above the text editor. The same result happens when I do Shift+Arrow and Ctrl+Shift+Arrow.
How can I return to a normal text editor behavior?
I fixed this issue by resetting all the settings and uninstalling extensions.
To reset your settings, go to Tools > Import and Export Settings > Reset all settings.
I am working on a template that have a General Link field, when I am trying to set the Insert link on Sitecore Content Editor I am getting below crash:
I am working on Sitecore 8.0 (rev.150121)
Even though the other General link options is working fine:
Insert media link
Insert external link
Insert anchor
Insert email
Insert JavaScript
I added a new field to the same template as a general link filed as well and it is working fine even for the Insert link option.
when I view the Raw value for the item I found that the link had a default value set to "" when I removed it and save all is working fine, the other testing link that I added do not have this default value, and the field on the template itself do not have such value or any default value.
This is a duplication of the question found on the Sitecore StackExchange here. Just to avoid any open question, here is the answer as provided in the same question:
The issue you reported was fixed in Sitecore Experience Platform 8.0 rev. 150621 (8.0 Update-4) and you can upgrade your solution to address the problem.
Please take a look at the reference number 416281 in Sitecore CMS release notes on for additional details on the fix: https://dev.sitecore.net/Downloads/Sitecore%20Experience%20Platform/8%200/Sitecore%20Experience%20Platform%2080%20Update4/Release%20notes
If upgrade is not an option for you, we suggest you implement the following workaround to resolve the issue on your current solution:
Place the attached Sitecore.Support.416281 assembly to the \bin folder of your solution;
Open /sitecore/system/Field types/Link Types/General Link item in the Core database;
Clean up its Control field;
Put Sitecore.Support.416281 in the Assembly field and Sitecore.Support.Link in the Class field;
Save changes.
Please download the assembly : https://www.dropbox.com/s/hl7ho6wmnca8u2y/Sitecore.Support.416281.dll?dl=0
From having done a bit of googling on this it seems that it is or at least was possible to do this with Sublime Text. I have seen multiple references to a preserve case button in the find and replace pane which looks like 2 rounded squares superimposed on each other.
However, I can't find this at all in my version of Sublime Text 3 (on Mavericks)...
Also I checked preferences to see if this option was somehow turned off but the only reference I could find to it was:
{ "keys": ["super+alt+a"], "command": "toggle_preserve_case", "context":
[
{ "key": "setting.is_widget", "operator": "equal", "operand": true }
]
},
in the default key map file...
Here is a screenshot of my find and replace pane:
In the latest Sublime 3 build (3059) there is a dedicated icon in the replace dialog to preserve the case. When toggling it and using the input shown in the screenshot, the following input string will be converted to the following output:
Input: "Xhis is my xest."
Output: "This is my test."
It's not exactly an answer to your almost 1.5 years old question, but maybe you (or somebody else) find(s) the following useful:
I wrote a ST package which includes a feature to preserve the case while editing multiple selections. It even preserves cases with separators like snake_case, dash-case, dot.case etc.
It is called MultiEditUtils. Here you can see the described feature.
Looks like it might have been a glitch in ST3 that was causing confusion.
I noticed that the shortcut key combo for replace has never worked for some reason and also that selecting replace from the find menu opened the find in file pane as opposed to the regular find and replace pane (where the preserve case button is). I only realised this after installing the soda theme for ST3 which showed the preserve case button in a screenshot.
Strangely, when I reverted to the default theme, the find > replace menu now works as it should and I found that the keyboard shortcut was being causght by another program which was why it didn't work...
I am using CFBuilder 2 (free version) and the insert closing tag functionality does not seem to work.
Here are my settings:-
Now if I type in a new openning tag e.g. <cfscript> I never get the closing tag. Am I misunderstanding what it is supposed to do or is there some other setting I should be changing?
This worked well in cfeclipse and so is incredibly frustrating.
Thanks.
Check the "typing" preferences page. There is a setting called: "auto-close tags". You probably have this set to "never". Try setting it to "When typing '>' of start tag". See attached image:
I've run into a problem in the Wokbox that seems like a Sitecore bug. When the "Items per Page" drop down is set to anything but "All", I'm able to expand the "Draft" and "Awaiting Approval" lists in the Workflow.
But when the "Items per Page" is set to "All", I get the following error:
Exception in MyWebSite: /sitecore/shell/default.aspx?xmlcontrol=Workbox&mo=preview
Message: Operation is not valid due to the current state of the object.
StackTrace: at System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding)
at System.Web.HttpRequest.FillInFormCollection()
And at this point, I'm "stuck" - and unable to revert my view back to anything less than "All" in the "Items per Page" drop-down. So, because I cannot revert back, I cannot do anything on the page, and any attempt to expand the Workflow lists (or do anything on the page) generates the above error.
Any thoughts on what is happening and how to fix this?
I followed up on this to keep from leaving this question unanswered. It turns out that this issue was related to another known issue. For the benefit of those who might be getting a similar issue, here's what fixed this:
The problem can occur when Sitecore CMS is installed on systems that have Microsoft security update MS11-100 installed.
Please refer to the similar known issue on SDN:
The Template Builder may fail when saving templates with many fields
The solution:
Try to add the following node to the section of the web.config file:
<add key="aspnet:MaxHttpCollectionKeys" value="5000" />