No announcement yet.

parsererror / syntaxerror when trying to post

  • Filter
  • Time
  • Show
Clear All
new posts

  • parsererror / syntaxerror when trying to post

    Got an error when I was trying to post a trip report with pictures earlier...

    error information: "200 parsererror SyntaxError: unexpected token < in JSON at position 0"

    Happened repeatedly. I kept on ripping out pictures, links, sections of text, etc until a portion of it would post. Then I would edit the post/ add more back in and cross my fingers. Sometimes the edited/added stuff would work and sometimes I would get the same error message. At one point I was adding one or 2 pics at a time until I could get them all posted.

    I think I had this happen just one other time. Maybe 5 years ago or so? I didn't do anything differently with this trip report than I have with all the others I've posted over the years so it was a bit frustrating. One thing I noticed was that typically I can get 10 pictures into a post. This time when I got to 8 pics I would get the error. I'm not sure if the error is popping up because of the number of pictures or because of some other issue with text or adding links.

    Not a huge issue overall as I said I've only encountered it once before but would be curious to find out what the problem could be. The trip report is under "other places" and called "Mohawk River State Park".

  • #2
    Makwa, since it's not happening consistently, and is not reported by others, I suspect it's an isolated issue as you mention. One thing to try is to clear your browser's cache, there might be some data that has gotten corrupted in your temp files.

    By exceeding picture size, or quantity you would get an entirely different message, and adding links shouldn't be an issue either.

    That sounds like a terrible idea.... What time?


    • Makwa
      Makwa commented
      Editing a comment
      Thanks Craig. If it happens again I shall let you.

      The only reason I mentioned the links was because once I ripped out all the pics and links I was able to post the text. From there I edited the post to add the pictures 1 or 2 at a time until I got a bunch in. Then I added the link to the google photos album and that worked so I then tried the other links and the error message came back. So I just abandoned those edits and left them out.

      Something must have gotten funky in there. It just wasn't the first post of the thread. It happened a bunch of times with the other posts where I had pics. Very strange.

      I'll clear the cache and hopefully that helps.

  • #3
    Let's see if this works... I've been getting the same error when trying to post a trip report with photos.

    EDIT: Not sure why I was able to post this picture. It's frustrating, as I put a lot of effort (a few hours) into trying to put together a trip report with photos, but the forum software won't let me post it.


    • #4
      I tried deleting and re-adding every single image... still got the same error.

      I tried changing every image so that it was uploaded to ADKHighPeaks instead of hosted on an independent site... still got the same error.

      I copied the text of my original post verbatim to ADKForum... and it posted just fine, without any errors. (I did have to make a slight modification to the "size" tags as the BBCode for ADKForum uses a slightly different format for the size tags than what ADKHighPeaks uses.)

      Soooo... I guess all of my Catskill trip reports are getting posted to ADKForum from now on.


      • Craig
        Craig commented
        Editing a comment
        By any chance did you clear your browser’s cache after the first error?

        The older software works a bit differently.

        I’ll look further into this issue and see what else I can find on it.

    • #5
      Yup, clearing the cache didn't fix anything.

      It seems to be an issue when posting topics/replies with a high image count. I get the same error when I try to add the images manually by typing out the "[IMG]" tags, and I get the same error when I try using the "Image" button at the top of the text box, whether I had the "Retrieve remote file and reference locally" box checked or not.

      Respectfully.. the WYSIWYG editor for writing out posts and replies just plain sucks. I know it's supposed to streamline the process and make it more accessible to everyone by eliminating the need to use BBCode entirely but I personally find it to be slow and clunky and frustrating. I can't speak for anyone else but I know that for me personally, it has contributed to me participating in these forums somewhat less often.

      (Some googling shows that VBulletin doesn't include any option to disable the WYSIWYG editor so this really isn't anything within the control of the forum Admins but I still felt the need to vent.)


      • #6
        originally posted by D Settahr 05-15-2022 @ adkforum

        Click Here For Full Photo Album

        Took advantage of a couple of nice mid-week days this past spring to check out another new area via an overnight trip by boat- the Piercefield Flow easement. The Piercefield Flow is an artificial lake formed by the Piercefield Dam on the Raquette River, just downstream of Tupper Lake. The shoreline of the flow is privately owned, but the state owns a conservation easement that allows for some public use of the lands adjacent to the flow. Public use is limited to the time period between May 1st and September 30th, and only to those lands within 300 feet of the shoreline. Camping is permitted at designated sites only. At present, only one such designated campsite exists- the Piercefield Flow Lean-to, which would be my destination for the evening.

        I elected to launch at the Setting Pole Dam at the outlet of Tupper Lake. A large gravel pulloff at the end of the road here allows for some limited parking, and there is a path down to the base of the dam that allows for the hand launching of canoes, kayaks, etc. While there can be some turbulent currents at the base of the dam depending on the flow, the river quickly turns calm as you paddle downstream.

        It didn't take long to reach the flow itself, and soon I was turning east to paddle up the flow. The lean-to is located on the north shore, not far from where the Raquette River joins the flow- maybe 700 or 800 feet away at most. Before long I was pulling up at the signed takeout for the lean-to.

        The Piercefield Flow Lean-to is located back up and away from the water, in a beautiful clearing in hemlocks and mixed hardwoods. It's a nice, quiet and serene spot.

        The lean-to had clearly been occupied not long prior to my arrival, judging from the piping hot bed of coals someone had left unattended in the fire pit. No matter, the afternoon was a bit humid and there were black flies out and about so I took advantage of the coals as well as some rotten logs I found in the woods nearby to get a proper smudge fire going.

        With the bugs held at bay for the time being by the smudge fire, and camp gear unpacked and arranged in the lean-to, it was time to relax. I spent a nice, quiet afternoon reading and hanging out in the lean-to site.

        My perception of the lean-to had been that it was a relatively newly-built one- constructed within the past few years. I was a bit surprised when I opened the log book to find entries going back much further in time. It must've taken the DEC some years after building the lean-to (or allowing it's construction) to get around to actually advertising its existence.

        I'd also sort of expected to see motorboats out on the flow and was mildly surprised that I was the only person there even though it was a weekday. I don't think there's any HP restriction on that body of water, but I did realize after the fact that aside from the hand launch at Setting Pole dam, there's only a small beach launch off of Route 3 by the Piercefield Dam... so access to the water by larger motor boats is essentially non-existent. And with dams pretty close both upstream and downstream there's not really a whole lot of surface water area to explore. I imagine that both of these factors probably help to limit the usage levels somewhat, especially in comparison with Tupper Lake just upriver.

        As the afternoon waned, I decided to take a short stroll out to the broad peninsula where the Raquette River joins the flow a few hundred feet from the lean-to. There were some more nice views from the rocky outcrop at the end of the peninsula.

        It's obvious that the end of the peninsula sees some occasional camping use... but any such use would be illegal. Normally, it would be a violation of the 150 foot rule, but in the case of the Piercefield Flow easement it would also be a violation of the regulation permitted camping at designated sites only. Which, to my mind, brought up an interesting question: If the lean-to is the only legal camping spot on the flow, what are groups expected to do if/when they show up to find the lean-to occupied? Your only options in those circumstances would be to either move into the lean-to with the first group (assuming everyone was friendly enough to make this work), or leave the flow entirely and make the drive of shame back home. It would seem logical that there should be at least 1 or 2 designated tent sites in addition to the lean-to, especially given how popular lean-tos tend to be.

        There was also an old mooring hook of some kind fastened to a rock at the end of the peninsula. What purpose it had once served I could only image. Tying up boats? The end of a boom stretched across the river to hold back logs until the time was right for sending them down river?

        It was still yet spring and I also found a few pink lady slipper blossoming in the woods not far from the lean-to.

        Satisfied with my short ramblings, I returned to the lean-to for more R&R. The afternoon progressed into evening, and soon the shadows were lengthening. Dusk wasn't far off.

        The evening remained warm but at least the black flies turned in for the night as they usually do. I crawled into my sleeping bag early and was up with sunrise, to be greeted by a warm and muggy morning. The black flies once again out in force, and another smudge fire was necessary for my sanity as I broke down camp and packed the canoe.

        I had plans for the afternoon to explore yet another corner of the Adirondack Park, so I packed quickly, dowsed the fire, and was back on the water just as my wrist watched signaled that it was 8 am. I did decide to take a quick loop out to the east before starting back to Setting Pole Dam, to check out that end of the flow.

        As one paddles further and further east up the flow, the water gets shallower and shallower. Eventually, there's a number of old stumps protruding from the murky and muddy waters- evidence that this was once dry land prior to the building of the Piercefield Dam and the raising of the water levels.

        Satisfied with my meanderings around the head of the flow, I turned around and paddled my way back to the Raquette River, and from there up to the takeout at the Setting Pole Dam. At some point after I'd set out the day prior, someone had opened up a portion of the dam to let more water out from Tupper Lake above, and I had to dig hard to get back to the small beach at the takeout. The potential for strong currents here is something to be aware of for anyone launching/landing at Setting Pole Dam.

        All in all, it was a short but fun trip. Again, the Piercefield Flow area seems to get less use than I would've expected otherwise- but this is likely due to the limited area to explore in either direction without portaging around a dam, as well as the limited options for accessing the water if you've got a larger boat.

        It's definitely a beautiful spot well worth visiting- but again, anyone planning to camp there should go mentally prepared to make the journey back to the takeout in the event that the lean-to is occupied, as there's zero options for legal overflow camping anywhere on the flow. Hopefully the DEC designates a tent site or two in addition to the lean-to at some point in the future.
        That sounds like a terrible idea.... What time?


        • #7
          I could find the same error message in the error_log

          We have increased PHP limits along with max_execution_time.

          I have done a test post with DSettahr 's original post (copy and paste) with no issue.

          Please report any further issues you may have.
          That sounds like a terrible idea.... What time?


          • #8
            Awesome, much thanks for putting the effort into figuring that out. If I see similar issues again I'll be sure to let you know.