Personally, I use Windows 10, Windows 7, Windows XP, and Linux on my desktop. What are you using?
<-- In this poll you can select more than 1 choice
Personally, I use Windows 10, Windows 7, Windows XP, and Linux on my desktop. What are you using?
<-- In this poll you can select more than 1 choice
Type message
Submit
Click edit
Type new message
Click submit and nothing happens (does not submit, as if the button were just a display).
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:50.0) Gecko/20100101 Firefox/50.0
Hi
“The minimum representable time is Friday 1901-12-13,”, https://en.wikipedia.org/wiki/…e#Representing_the_number
Humanity has surpassed technology. These days that is a rare thing.
The minimum age is 1, that's why it won't allow you to set yesterday's date. I've increased the maximum age from 100 to 120, now matching the server-side validation, previously the JavaScript date picker was limited to 100.
I think you missed your mark. Currently you cannot enter a birth date for 120. The max appears to be 114. Anything older and the site gives an error. Which should be acceptable for now, but long term, say 4-5 years from now; that may need to be addressed.
I think "Unknown location" is also thrown when they visiting a unexistent page or do not have enough permission to see a page.
Then it should read something along the lines of Viewing 404 page or Viewing permission denied page or Being asked to login or something (anything) other than "unknown"
Quote
Better User Tracking
Locations are now tracked much more accurately, including support for customized locations and page names.
Guest listed as "unknown location"
As with all previous press releases, I do not actually see everything that is promised. However, if that is the case, is this then a bug since it's still an 'unknown location' for a guest?
edit: Reported as bug since the press release seems to suggest this is a bug. Though I suspect it will be' forgotten' in order to reach whatever internal deadline
Abuse_and_Troll_Test how about your own installation? are you having the same session expired experience?
Yes on my server, on the servers of few other folks here, and even on localhost which is why I suspect this is not something that can be ignored.
WoltLab claims this has been addressed on RC1 so we'll have to wait and see.
It has already been fixed yesterday, but the changes are a bit more complex, so I haven't applied them manually yet. However it does work properly with RC 1.
I look forward to verifying these changes once applied. Thank you
^ A quick follow up after giving it more thought
If a simple IP change causes this, you're going to annoy the hell out of mobile web users. That said, I still receive this error even on the same IP address (as previously stated).
I've seen your IP address rotating in a quick manner, sometimes three different ones within 15 minutes, each originating from the same ip pool. This is an issue because the system can no longer recognize your session due to a mismatch with the stored data, rejecting the data provided by the browser.
Reloading fixes the problem, as your browser will transmit the auth cookie again that is used to transparently log you in. AJAX requests are designed to ignore the auth cookie, which causes them to always reject your request on mismatch, no matter what else is provided (XSRF protection).
* sigh * -- I think you're deferring and avoiding a yet to be resolved underline issue. While it is true, I have been jumping through public wifi, this error happens even when I'm not moving and on the same IP. I predict upon release, this is going to affect other people and you'll still be forced to look into this later. It would be better if you do so before release.
There are plugins made for this use, but when WoltLab includes that into the core, it would be nice. But we are near to the first release candidate...
sigh
I think it's being rushed and important things are being neglected in order to push a release on a scheduled date. The fact that I had to 'fight' just to have a security concern resolved, is proof of this.
Don't get me wrong... I like WoltLab Burning Board and I do like where the new software is overall going, but I do think it could be better.
These days a simple password is not enough to secure your administrator or moderator accounts. I think it would be wise to add an optional 2 step verification process
Display MoreFollowup respectively correction
Abuse_and_Troll_Test : Sorry, I got you partially wrong, thus I had a different situation in mind. You as well as Geronimo were right, so needless to say that I simply had to delete my reply in order to not confuse readers. Beg your pardon
and consider my intrusion as kind of non-existing. Well, guess it's time to offer a cookie and asking "Still friends?"
So, never mind me, the thread's still open for discussion and I'll stand in the corner, writing 100 lines on "Why it's important to read correctly".
![]()
No worries.
The given page is no article. And at the moment, AMP support is limited by WoltLab for Articles.
So in otherwords, it is useless for most anyone not using the cms. This really needs to be made site wide.
It's available for download.
^ This.
I do not understand your line of thinking duplicate Tester123 My request is to have the whole preview available here for everyone to test. We already are testing the forum, why not everything else here?
As previous noted by the staff, core 3.0 would have AMP support
QuoteArticles include full support for Accelerated Mobile Pages, a heavily stripped-down version of the site, designed to load extremely fast as possible on mobile devices with low bandwidth available. AMP pages are recognized by the Google search engine and help your content to achieve better visibility and thus gain more visitors.
source: https://community.woltlab.com/…-suite-core-3-0-articles/
the site has failed
I prefer to install google custom search in my site, it gives better result than built in search engine.
The problem with that is the same with users going to Google. The results may include ads or suggested content that points to elsewhere and away from your site.
Well, sounds simple enough but it isn't.
If you really want to create a whole new search engine those numbers aren't that crazy.
I mean whole companys out there are doing nothing else than developing their own search engine, even if many of them just work arround the lucene engine like solr and elasticsearch...
And the main problem is still that most forums have only php and mysql as backend and both of them haven't really good and scaling options other than a regular full text search.
Google started in a car garague and only needed 1 PC to run it. Of course it has grown over the years since... It after all is indexing the whole internet.
What I seek is not to index the whole internet, rather just 1 single site. It does not need a billion dollars and it does not need a whole data center, just 1 pc for 1 site.
Facebook has it's own search engine for 1 site, it's own. I'm sure the same thing can be done for a forum.