Can't edit the post for some reason; but where it says "native" in the config file, it should actually say "file". Changing it from "native" to "file" still does not fix the issue.
Changing the driver to "cookie" and using cookies seems to have solved the issue for the user; however, this is not ideal. This issue initially came up when we were using memcached for caching and sessions so we changed it to files to test. Ideally we would like to switch back to memcached, but the issue for this user still persists using both the "file" and "memcached" drivers.
Sorry for the spam, editing my posts doesn't seem to be working.
Switching to cookies did not prove to be viable as the data exceeded the limit. The same issue is also happening with the database driver.
This is the strangest bug, but has a temporary solution. The moving the same code around to different functions and routes did keep the flash sessions alive and they never disappeared. The issue was in the HTML/javascript. The button used to submit had an onclick confirm on it. Removing the onclick and confirm solved the issues. Moving the confirm to an external javascript file did NOT solve the issues. The only way the user would receive the session messages is if that confirm was not present at all.
Weird bug, weirder solution. If anyone has any idea as to why this happened, I'd love to know.
Sign in to participate in this thread!
Laravel
Laravel News
Laracasts
Laravel Podcast