Terminated request ...

I posted an image series for a fairyfly with lengthy, but valuable, remarks pertaining to the entire series:

When I tried to enter the remarks on the first page, though, I got the error message, "terminated request because of suspicious input data". It appears the problem is a new length limit has been imposed. My work-around was to continue the remarks under the second image. That would not have been possible, though, if I only had one image. Is this new limit really necessary, and is there a way to place lengthy documentation under a single image's remarks? Many of my posts document significant research pertaining to the subject.

01 SEP 2018 Follow-up:

The problem remains. I put a continuation of remarks for another image with long remarks (Sucrose flotation) on the second image page again due to length limits. However, this is not an option if there is only one image. I suggest that until such a time that the Powers That Be reconsider such a blunt instrument to screen for spam, that the image's comments section or even this topic thread be used as a repository for long remarks. I have not encountered any length limits for comments (yet, at least). Readers should be asked not to directly replying to such comments, since that will render them un-editable.

Now, to put a link on your image page to your remarks that sends the reader directly to them (instead of the top of the page), first post the remarks as a comment, then save the resulting webpage as an html file (File > Save as > Webpage, HTML only in Window Explorer). Open the file in Notepad and search for the string "a id=" (without quotes) that immediately precedes your comment's title text. The long number that follows (2687055 in my example) should be placed after a "#" at the end of the URL for the page in your link. For example, to get to my remarks for (Sucrose flotation) (which I put here as an example), put this at the end of the remarks edit block for the comment:

[url=https://bugguide.net/node/view/1481234#2687055]Click here[/url] for Remarks.

This will look to the reader like:

Click here for Remarks.

Contributed by Edward L. Ruden on 1 January, 2018 - 4:47pm
Last updated 2 September, 2018 - 3:15pm

Sucrose flotation-sieving extraction from soil

Please do not reply to this comment directly so I can edit it as needed. This is an example of a work-around to the subject length limit issue. See the follow-up in the main topic text for details.

Due to length limits, I was unable to list the instructions on the main page of the subject post in Active search and collection equipment and techniques, linked here:

Procedure (click number to go to image page):

1. Place a pint of soil in 3 gallons of water in a 5-gallon bucket.
2. Break up, mix, and swirl gently but thoroughly by hand, wait 10 seconds for heavier material to settle, then pour off liquid with suspended particulates through a 1 mm mesh kitchen strainer into another bucket. Discard material that settled in the first bucket, and that trapped by the strainer.
3. Remix and pour liquid/particulates into a second bucket through a 0.5 mm mesh kitchen strainer over a 6 inch diameter PVC DWV socket coupling tube with an 80 mesh (0.177 mm) screen glued to its bottom.
4. The tube is needed to contain the liquid until it passes through the screen and support the strainer. If water flow through the lower screen slows to a trickle, pour the unfiltered water back into the source bucket, proceed to the next step, then repeat this step (with a clean screen) until you can get all the water to pass through. Discard the passed liquid.
5. Wash material trapped between screens into a 1 quart mason jar using a funnel hot-glued to a canning lid ring.
6. After a few minutes, pour off and discard the flotsom and most liquid, and replace it with a 1 molar sucrose solution (342 grams of sucrose per liter of solution) to which 1/4 cc of UltraClear(TM) flocculent has been added. Cap and shake the bottle gently. Wait a few minutes for lighter material (including arthropods and such) to float.
7. Pour flotsom slowly through the 80 mesh screen. The tube is not needed at this stage since the liquid is of small quantity, so the tube/screen assembly may be inverted (tube on bottom) to simplify the next step.
8. Flush screened material with fresh water into a pint jar with a funnel.
9. After things settle, retrieve solids from the bottom of pint jar with pipette. Place some in a flat bottom petri dish no more than one layer deep. Cover with water to a shallow depth. Multiple samples may be needed if there is too much detritus. The image shown is a 15 mm square area of the petri disk. There are many things alive and moving at this stage, mostly nemotodes (long thin worms). A 0.75 mm long ostracod is centered in the field of view. It is aquatic but still alive, so must have been stranded on the shore recently.
10. Inspect sample with a microscope. There may still be a lot of detritus, but the particles are small, and mobile specimens should still be alive and moving. Their motion will greatly facilitate their being spotted if they are not buried under more than one layer, as suggested. This is a higher resolution crop of one shown for the previous step. The ostacod is now center left. A springtail can be seen top center. An insect larva is bottom center. Several nemotodes are in the upper right quadrant.

… Edward L. Ruden, 30 August, 2018 - 10:13pm

Another

I had the same problem trying to turn a Google maps URL into a link (with link text not identical to URL, which may matter): https://bugguide.net/node/view/1464264.

… John F. Carr, 1 January, 2018 - 7:09pm

Markup url links are fine

The problem in my case appears to be simply one of length, not content. I didn't have to change any content at all. I just had to break it into two image remarks sections to avoid the error. Indeed, I use Markup to link to Google maps in the first page without a problem. The following code:

[url=https://www.google.com/maps/place/29%C2%B056'25.8%22N+97%C2%B055'16.0%22W/@29.9405,-97.9232998,17z/data=!3m1!4b1!4m5!3m4!1s0x0:0x0!8m2!3d29.9405!4d-97.9211]29°56'25.8"N 97°55'16.0"W[/url]

Results in:

29°56'25.8"N 97°55'16.0"W

… Edward L. Ruden, 1 January, 2018 - 7:55pm

Disclaimer: Dedicated naturalists volunteer their time and resources here to provide this service. We strive to provide accurate information, but we are mostly just amateurs attempting to make sense of a diverse natural world. If you need expert professional advice, contact your local extension office.

Contributors own the copyright to and are solely responsible for contributed content.
Click the contributor's name for licensing and usage information.
Everything else copyright © 2003-2024 Iowa State University, unless otherwise noted.

Bugguide is hosted by:

Printer Friendly Version