• I have purchased the premium version of this product and am fighting two issues with the voting system that have been listed here as resolved. In my opinion they are anything but resolved.

    “400 Bad Request”, header field & cookies???”

    http://ww.wp.xz.cn/support/topic/400-bad-request-header-field-cookies?replies=14

    I changed the Apache Config to the suggested parameters and it still gives the cookies error. Fine… set to unlimited votes. Even though that is not what I wish to do.

    But this is marked as resolved when as posted by PaulMighty that this is not an option for sites hosted in a shared environment where access to the server config is not available.

    The issue still exists so how can this be resolved?

    “There was a problem saving your vote, please try again in a few moments.”

    http://ww.wp.xz.cn/support/topic/there-was-a-problem-saving-your-vote-please-try-again-in-a-few-moments-5?replies=7

    So the only viable option you have suggested is to use a default WP theme with no other plugins working but the NextGen plugins? That kind of defeats the purpose of the 30,362 other plugins out there.

    Like a Scorpiion4984 I have disabled all plugins except for Nextgen and still have the same issue.

    How is this resolved?

    I currently have over 200 pics on my website, and plan to add more, and the voting is crucial to the core of the website.

    http://lingeriemenlove.com/styles/

    Any useful options… apart from marking this ‘Resolved’… would be appreciated. I am seriously pulling my hair out over this.

    https://ww.wp.xz.cn/plugins/nextgen-gallery-voting/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author shauno

    (@shauno)

    Hi Temujin2116

    The cookie problem only happens when sites have a very low ‘LimitRequestFieldSize’, and a large amount of images to be voted on. This is an edge case, and not what the majority of the plugin’s user have.
    If a user is in this position, they should consider upgrading their hosting.

    I will revisit making this more efficient in the code at some point, but that only delays the problem, you will ALWAYS be able to run out of ‘LimitRequestFieldSize’ if you have enough headers being sent with each request.

    Thread Starter Temujin2116

    (@temujin2116)

    I apologize Shauno. I suppose I am venting at you when I should be venting at WordPress.

    I think WordPress is the biggest piece of shite software I have used in 20 years in IT. I think it is the Windows Millennium of Web Apps. WordPress breaks the very plugins that make it useful with every update. Many of the plugins break each other.

    The WordPress plugin search system is next to useless as most of the results of any search return plugins that have not been supported in years and are not compatible with the current build.

    If I could find a viable alternative to a Web voting gallery software I would use it and dump WordPress all together. If you know of any such software I would love to know. I have spent many hours looking but can not find anything that does what your plugin does.

    Your plugin is brilliant when it works. I just need to get it working…so I will rephrase the question… 🙂

    Could you explain to me in layman’s terms…I am not a code monkey 🙂 … the issue regarding…

    “There was a problem saving your vote, please try again in a few moments.”

    If you could speculate as to the possible cause of the problem I would appreciate any effort to point me in the right direction.

    Plugin Author shauno

    (@shauno)

    No stress, I’m not offended by your venting 🙂

    The message “There was a problem saving your vote, please try again in a few moments.” normally doesn’t have anything to do with cookies, so there might be a legitimate problem with the voting on your site.

    If you disable all other plugins (other than NGG and Voting), do you still get the error? I looked at the URL you provided in your first post, and I’m not getting an error when I vote?

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Resolved… but NOT resolved.’ is closed to new replies.