Time for a heads-up that we did an upgrade of the site today! The last version the site was running on is the recommended production version 1.1.8 but this is our current 2.0 snapshot. There is no install package for this, its a manual upgrade only and not recommended for real production sites AT ALL. Franky its probably a bit early for this but we really need to get some testing and feedback going.
Now we're still fixing bugs and issues. Some real and some just a result of the manual upgrade process. As always you may need to do a hard refresh to clean out your browser cache as the theme files are completely new. Once things settle a bit we will update the site to php8 as well.
Please report everything you still find so we can get to doing what we do best, creating more bugs ... The best place to report the issues is on our GitHub issues tracker (https://github.com/elkarte/Elkarte/issues/new/choose) You can report them here, but that means someone else will have to add it to the tracker, which does not always happen so known bugs are simply overlooked.
It's great to see Elkarte back up, Is there a list of changes for 2.0?
Great news .
Thanks for the awesome work.
Not really, I can try to come up with something that users may care about.
There was a tremendous amount of restructure to the code, (as we did in 1.0 and somewhat in 1.1) which a typical user would not care about.
One new item that folks can test is better emoji support.
You can add all sorts of them :smile: to your post just by entering a : then the emoji name, like :smile as the simple example.
There are 100's of available ones, currently the forum as over 1000 available. They are all SVG icons so they scale up/down nicely and are crisp. Once you enter the ':' and start to type in some text you will get a selection box of emoji that match .... some examples
:rolling_eyes: :airplane: :elephant: :abc: :camera: :cat: You get the idea :wink:
Was getting a little worried about y'all here.
Thanks for bringing it back, I get a JSON error when liking your post @Spuds and the mention autocomplete doesn’t appear to work.
I’ll log them both on GitHub later
Thanks for the report, and more so logging them :smile: I'm working on a quick (hope) fix PR to address some of these.
Honestly - this is the best mobile theme I've ever used on a forum. I love it.
That's fine no need then, sometimes major changes and this is just easier. :wink: (smiley worked with adding : )
Thank you for continuing to develop a new version of the engine ElkArte.
Tried to like a post...
in the popup window, and the following as the POST response:
<h2 class="category_header">An Error Has Occurred</h2>
<div class="errorbox" id="2" >Invalid argument supplied for foreach()</div>
I've tracked this one down :smile:
The cause is do the 2.0 "conversion" and one table column not being updated to the new values. It should be adding your like, its the member notification of that like that is causing the error. I'll get this fixed tomorrow, need to test an update query first.
Glad its working well!
2.0 did a fair amount of changing the existing CSS to Flex and Grid layouts to the frequently used areas. That allowed a lot of crud/tricks/float/table/etc removal since (flex./grid) were designed to do what we need. The goal (at least for me) on the beta was to have things look mostly the same, but with a new temp[ate/css structure behind it. Its far from a template engine or anything like that, but a refactor of the old layout to current capabilities/standards.
Cool! This will be awesome! Keep up the good work guys!
Another tidbit - this thread has a lot of overflow! The source seems to be the code box.
Ah yes, I see the code overflow when I narrow the browser .. solution, don't do that :laughing:
I'm in !
Why didn't I think of that? ;D
I made a CSS change which should have fixed that grid blowout issue.
Me too. All of a sudden the site was down. :o
Glad you are back with good news! :smiley:
Glad to see Elkarte online :cool:
--- edit ---
seems that inline attachments are not visible, here an example https://www.elkarte.net/community/index.php?topic=6037.msg42918#msg42918
Thanks, I'll add that to my list :sweat_smile:
I put in a temporary fix for the attachment not showing and likely a few other issues here and there (same root cause)
The final fix will likely be a bit more involved, assuming I make up my mind what I want to do:confounded:
When I click on the "mark all messages as read" button, there is an endless looping.
Shown in the screenshot.
I had something similar, I was not able to quote a message, but after cleaning the cache files in my browser the problem was solved.
after clearing the cache in the browser Chrome, the problem is not solved
I'll log it so it can be looked into
When you have a multi page topic, reply counting restarts each page, so on page 2 you get no mention of the first post, then it’s reply #1, reply #2 etc. And again on page 3.
Already reported here https://github.com/elkarte/Elkarte/issues/3553 ;)
And it should be fixed now
I refreshed the stie to the current state of what we have in GitHub. So some bugs will have been fixed, some "not yet" and likely one or two new ones added.
I have NOT updated the language files. In 2.0 they have been moved to a more sensible location / structure, but as of now all I had time to do was the default.
The editing of the signature in the profile area, or the display of the current one, seems to be badly messed up. Also the custom language setting is ... gone?! :o
The language issue is likely since I have not installed the packs yet, hope to get to that in the next day.
Not sure what you are seeing on the profile signature, it looks fine on my system. 1st be sure flush your browser cache as the CSS has changed. If that fails to fix it, which theme, and browser are you using and could you provide a screen shot as well?
The signature should be bbcode, right? Not that:
Thanks for the extra details
Yes that should be showing the BBC but its instead showing the rendered html., I'll get that fixed soon.
I noticed that Notifications and Messages menu buttons are highlighted (yellow), bot I have no new notifications/messages, and some of PMs have no name in "From" column (on PM main page) but when I go to conversation I see author
Is that on the beSocial theme ?
Fixed! The signature edit box now displays bbcode correctly. :D
Nice quick reply by the way. The related addon won't be needed once this 2.0 is finalized.
Hey its yours :D
I gave you a shout out on github as well. Thank you for the idea and work on QRR
For me, the search and the account link disappear from time to time. For example, when I have modified a post. Only after a reload they appear again.
I've seen that as well but have not (yet) been able to track it down.
Wait, where? I don't see it. >_>
Do you have quick reply enabled in your profile look and layout?
Yes, rather I guess I meant to signal a failure on my part to see any difference with how it's always been since all the way back in SMF?
The old one was a plain textbox (assuming you have full editor off) after the menu, breadcrumbs and posts (Link-9946)
The new one is more in the flow of the posts, appearing as the last post, with your avatar etc but with no text. (Link-9944)
See its so clean now you did not even notice a difference :smiley:
Updated the site again with the latest commits from the Github repo.
This means, some bugs are fixed, some remain, and some new ones were introduced with the brilliant goal of Fixed > Introduced !
There were fixes pretty much everywhere, and there are still several that I am aware of but the fixes are not yet committed. There were also some theme fixes to both light and beSocial.
As always report them as ya find them.
And another round of update was applied today.
Once again, more bugs fixed and maybe some introduced!
Be sure to refresh you browser cache (if you wee any problems)
Before I forgot, should some one see if this small site icon or favicon things be made easily manageable because most ElkArte sites don't show this properly especially in site's shortcut. Not that it is important but for the sake of completion may be.(Link-9990)
Thanks, I had forgotten about that (it should be back on here).
I think the issue comes from us moving away from the old favicon.ico (some time ago) and instead one needs to have a mobile.png file in sites root. That should allow the old favicon in the browser tab as well as a proper mobile shortcut icon. Its called out as
<link rel="shortcut icon" sizes="196x196" href="......mobile.png" />
Honestly? I think it's pretty crude at this stage. A lot of the detailing seems to be a backwards step from the original. It works, but it's visually clunky.
However, obviously I can make it look any way I want it to look, if I really want to, so...
As always, details and specifics are welcome.
Honestly? Too long a list. The short version is that the overall impression is crude, thrown together, a collection of code with no overriding vision or aesthetic. The board icons are an obvious example.
The finished result does not necessarily have to reflect my current ideas on aesthetics. I'm happy to admit that other guys are capable of making coherent themes, which look great, and which contain things I may not have thought of myself. However, IMO, as things stand, this ain't one of those themes.
And TBH I cannot see the point of cramming the info centre over at the right side of the forum. Yes, it's very simple CSS to change it, so no problem there. Yes, it does fill up a bit of space on wide screens. But it does that by making the whole page look unbalanced, so no aesthetic benefit. It also only applies to the board index, so as soon as you are inside a topic you are back to the same problem of chasing sentences fives miles across your screen. Really a sane max-width on post content is what's needed for easy reading. Basic typography stuffz. Has been known for literally centuries. :)
The board icons are what they have been since 1.1?, so no change has been made there, at least that I recall. But I know some folks were unhappy with the SVG icons vs PNG ones.
The info center on the right (the 2.0 theme "what do you think about" is a separate topic) is simply a test to gather feedback. Obviously its what Xenforo does on their board index and there, as here, it goes back to the to a wide a view on the topic listing and messages. Just a test to see how many folks would come by to poop on the statue !
I'm not sure how much effort needs to be put into wide viewing vs narrow viewing. Its hard to get a feel for what the predominant format is now, although I tend to feel its laptop and down (1920 and down, and even so 1280/1024 and down). One could add sidebars to all of the main areas, but that also gets busy, to much information to take in at one time, too much visual clutter.
Anyway just putting things out there to gather feedback on what folks expect and how they interact with sites these days, honestly I've not seen anything "new" in forum layout, but that may be an indication that folks don't want to re-learn an interface for each forum they may participate on, they all tend to be familiar so they are easy to navigate. I'll record your vote as old way better ;) Thanks for the feedback.
Site icon is working now. Great.
I am not about other things in specific so I rather not comment except good work so far. Keep it up.
I suggest running your Darktanion variant through this: https://webaim.org/resources/contrastchecker/
As things stand, it comes nowhere near meeting basic a11y guidelines.
And now the site won't let me change back to the Light variant. I'm stuck on Darktanion. :P
Looks like you have some sort of bug with variant selection.
Seems to work as long as you do not use the "Forum Default" selection area. But yes that overall area is still not working as it should, something else to look into :P
If I get motivated I'll do that! Overall it was mostly a test (for me) to see if I had broken out enough color vars in the CSS to make at least basic styling "do-able", I doubt it will go anywhere.
Yep, I got myself back to the Light variant somehow. Can't remember exactly how I did it, but basically "ok, try this now and see what happens".
The WebAIM site is a very good resource. I use it a lot. One of the things I have noticed about dark themes is that I find them much easier on the eyes if everything is balanced for contrast ratios. IOW, body text, link text, titles, etc (and taking into account that a larger font-size and/or higher font-weight gives the visual impression of higher contrast for the same colours). If not all backgrounds are the same, I often don't use the same text/link colours on all backgrounds.
I tend to use the contrast checker a lot as a starting point, then tweak things from there to compensate for font-size and font-weight. I don't always go for passing WCAG AAA either. From memory, I think WCAG AA is the usual standard for most countries, and dyslexic users (not an insignificant percentage) find too much contrast makes their dyslexia worse (the text starts crawling around the page for them) so there are arguments for not using too much contrast in a default theme. Black on white, or the inverse, are way too harsh, IMO.
I installed the Wave plugin (I think its from WebAIM) for chrome and that seems to do good job at pointing out problem areas w/o having to have a site published, so good for development. I ran it on light and made a couple of alt text (all those alt="") and link fixes (a few text-less links), colors were fine. Only checked a few of the main pages.
I'll look to see what it takes to get to AA on the dark theme. Agree about to much contrast, for me it get harsh and for dark themes I tend to like ones with a touch less contrast, probably why Darktanion ended up where it did. It was one of those color wheel changes on text/links until, yeah that feels good to my eyes.
Glad you got to reset the theme. That theme choice area of Profile was redone in 2.0, it used to use the admin controller but now its stands alone in the profile controller, so yeah, a few bugs added.
So another round of updates were applied today. Some of these were already "live" but had not been committed to the repo, so what we have now is what is really
in the dev branch of the repo.
- Some more random CSS cleanup, mostly padding/spacing and the like
- Committed the chart.js items for stats view, that was discussed in another topic. Also now in profile stats, those little donuts that showed popular boards by posts are now SVG created on the "fly" icons. You no longer have to deal with the old sprite image which only had distinct wedges and was more difficult to color to the theme. Now you can change the color with ease.
- The JS/CSS minify was updated so now you can choose to minify files but NOT combine them into one. Some folks like that better. This was an update that also included JS defer changes and some other minor cleanup of inline JS. Unfortunerly one of the JS compile options we had was a google service that did code optimization as well, but that service has been flagged as depreciated so we can really use that any longer. Now its simply a whitespace remover.
- Added, as an experiment, several other video embed sites, Facebook, Instagram, Twitter, Tiktok I'll do a separate post on that.
- Open graph metadata and site schema is now an option. If you look at the page source you will see the tags that are added by the option (its not all in the head, so look at the bottom as well). This data is not on all pages, its primarily on topic view, board and topic index pages. It will use the appropriate description for the page and will also make use of attachments (from the first post only) to help announce the item. Basically the open graph stuff is used when you share a page on a social site and the schema stuff is for search engine consumption.
- Another large batch of fixes to various areas, to numerous to list, still lots to go !
Great news, specially for metadata & site schema, IIRC this feature was asked some time ago to be implemented
Slowly getting all the features in place. You will notice the schema org data in its fullest form only when viewing the first page of a topic.
If there are other features that have been requested and are not in place, don't hesitate to post a little nudge reminder :smile:
I haven't get involved in this for quite some times (may be because I am not sure how) but so far I can only see that the 2.0 development is doing great. Thank you all for keeping it up and moving to the right direction.
Updated again today .... the changes that I recall in this update are
- Quick Quote .... The button is currently off until text is selected but that is an ACP option. The QQ feature is on the topic display page assuming your have quick reply on. Its on the full post page when you select text from one of the topic reply's down below the post and drafts area. It will also be available on the PM reply page.
- Improved Quick Moderation. Only checkboxes now, once a box is checked the menu will be stuck to the bottom of the page (when it reaches that of course) That bar should be available on the display page, search page, and recent page (I think) The button counters have some smarts in them, they will only increment based on the number of messages selected in which that action is available. Certainly not perfect but at least its a start..
- Improved emoji support, now almost 500 additional images are available and one of the sets was changed to a library that is better supported. This also includes the fix so the dropdown menu is better populated (that is the selection menu you get when you enter a : and then some text, you do need the full editor, the select menu is not available in the plain text area, unless someone wants to write that code)
- Fixed some of the contrast issues on the dark theme, still just a WIP
- Fixed more theme issues and various bug fixes all over the place.
That is all for now, more goodies to come :smiley:
Placed the latest code on the site.
Changes that I recall:
Fixes / Updates
- Quick Quote now displays its button by the text that you highlighted. This replaces placing it with the other buttons as those may be off screen. This should provide quick access and visual clue that the function exits. It should also now behave better on double/triple clicks.
- Buttons. We have lots of buttons, and they were often created in different ways. This update begins to consolidate how they were created so the markup is consistent and provides easy ways for addons to hook into those button strips. For example on the display page where it has | quote | quick edit | like | more ... those were coded in the template requiring code edits to alter/add. Now they are a simple array definition that can be changed as needed. Same goes for buttons in display, search, pm, recent are all done the same way.
- As a bonus to the above, the button code is a lot more complete, adding icons or counters or checkboxes can be done. The display button strip was one of the last PNG sprite holdouts, those icons are now SVG like the rest of the site, you may notice the change.
- The PNG sprite used in the headers (some areas) has been removed and those icons changed to existing SVG.
- Added a new (experimental) BBC code "icode" This still needs some work as code blocks are a PITA and I have not addressed all the code/icode combinations, including nesting's so still a WIP But now if you want to place some code inline you can (no its not in the editor toolbar, should it be?)
- Added basic Markdown support in the editor. so typing **something to bold** will result in something to bold or *something to italic* will result in something to italic maybe even quick inline using fenced tick ` marks. And yes combinations of that inside standard bbc icode blocks is not going to work right. Code blocks were complicated enough so consider the last two experimental. They will mostly work, but there are problematic combinations.
I'd say that the icode button shouldn't be into the editor, we already have too many buttons. I will open a new topic for this, probably could be a good idea to group some buttons, specially on mobile.
Sounds like a good topic ... most of those toolbar buttons are never used, and now with some markdown available, perhaps even less at least for me
I think that's largely contradictory with the especially on mobile comment. **** isn't that easy to type on mobile, imho. Mobile is perhaps the only place where I use those i/b buttons. (But most of the buttons can probably hide behind a few dots or something, particularly if the user can configure which ones they want to hide behind it.)
Fair point, I did munge up a couple of thoughts :monkey_face:
I would think we would keep basic format buttons B, I, U, S, and then maybe some commonly used,, Bullet List, Code, Link ... Just thinking about the ones that get used, and ones that also render "OK" in wizzy
The Others would, of course, still be in the Reply/Modify/Preview page aka the full editor. On QR we could also perhaps add dropdown with the others, or not, or maybe just on mobile.
We can also entertain adding in a @ button since that is also not quick access on mobile (well does depend on the keyboard in use)
Adding in a way to add attachments in QR would be awesome IMO
The program is beautiful and cute.
Can not be relied upon to build a large forum.
For a number of reasons, including:
1- There are no seo features, a description of the site, sections and topics, no sitemas, and no search engine friendly links.
2- The template modification system is very annoying and tiring.
3- The membership system is frankly very bad. And not tidy.
Incorrect, read the thread before you post wrong information. 2.0 contains both OG and SCHEMA meta data
please stop registering and posting with double accounts, that's not allowed here.
Did another site refresh today. I'll try to highlight some of the changes
- Another batch of PHP 8.1 updates. Some of these were blockers, some were simply error log warnings. Either way the bulk of them should have been addressed
- Fixed a few install issues, still have work to go
- You can now use a gravatar as a users default avatar (in place of the shadow bust), several themes to choose from as well. Thanks @Trekkie101 for the idea
- Several search tweaks, outlined them in another post. Most minor but should help improve overall results and their presentation.
- Improved / enhanced webP support to allow admins to accept webP uploads but convert them to png or jpg (system will choose based on the upload having transparency or not)
- Improved the attachment upload code, again for the above webP image, the interface will show the image was converted (name extension) and the space left etc. is correctly updated (attachment resize is also all built in). Several tweaks for keeping track of the values as items are added and deleted.
- Adjustments to the meta description tag to better leverage the open graph and schema data that is created.
- Lots-O-bug fixes plus more open issues closed
- Major updates to outbound mail. When using the mail list functions, outbound email will now include a true HTML version. This will be seen when getting posts text by email. That is not as easy as it may sound, HTML in email needs (or should) follow many rules in order for the HTML to be used/understood. Without getting to deep into the details, the basics are the HTML is wrapped in a table structure, its has its own style sheet, needs to be html4/css2 level, and a few other gems. It also has to account for any "fancy" css we use in our parseBBC output and simplify that so it can be consumed with a basic CSS styles, suitable to email embedding.
- Overall better email emoji, quote, code, etc support (catching up with all the HTML changes we made to those tags). These improvements are in markdown and bbc conversions
- Continued theme tweaks (all variants) as issues are noted.
Probably some other things I'm forgetting ... and of course likely introduced a few new bugs.
It would be nice if Outlook actually supported anything that advanced. :P
LOL ... as I read about the HTML "support" in various, still in use, mail clients well :exploding_head:
And another site refresh last night ... there were a few db changes, so for anyone running a copy see the upgrade script in install. Added one col to boards, changed session size/type in 3 areas, moved some theme to be site settings.
- Improved Emoji support for mobile
- Small improvements to site metadata
- Added ability to individually turn off moderation and user logs (if core logging is enabled at all)
- Moved draft selection to "load draft" button, better visibility, less clutter
- Added additional info (if available) and categorized admin support area php/server/ElkArte
- More email improvements, mostly on inbound processing but some outbound improvements as well.
- Many bug fixes, closing old github issues
- Many areas of general code cleanup
- Moved all logging actions to single area in ACP, still need to overall ACP
- Moved some theme options to site options (show edit, show group, show avatar, ..)
- Added ability to enable -old post warning- on a per board basis
- Continued CSS normalization across the variants / removal of unused classes / fold some odd single use classes into core ones
- Improved unsubscribe from XYZ tokens that are sent via email
- Improved code block protection for markdown, centralized / exposed protect code block functions
- Search now uses date pickers (in advanced) instead of old/odd/confusing older/newer days input
- Package server screen was missing tabs
- Standardized on varchar 128 for session data (was char or varchar 64)
- Continued theme cleanup and fixes
- Improve / differentiate between full word and sub word matches in search highlight
- More php8.1 updates
- Allow use of gravatar as default avatar (selectable set as well)
- Other stuff I forgot, see github commits should you want details
After removing that function, it just fails on the next, followed by the next etc.
I manually added the old_posts thing and the forum works again.
Thanks, I'll take a look and see what I mussed up! When I did the site upgrade I did it the old manual way :innocent:
I’ve found the failure doesn’t seem to be related to the steps, as every step can produce a fail, was a bit bizzare - so I just manually did them.
How "beta" is the dev version at this point? Bugz included being a given, is it tolerable for mid -size site testing? Organic users are a great testing ground. Does the upgrader work from 1.8?
I would certainly appreciate more real testing :smiley: its needed to shake out the bugs. I'm sure there is still a fair amount of error log spam as well, every so often I go through the logs and fix some of what I find. The real start of Beta is when (at least to me) new features are no longer being added, so feature freeze and you just concern yourself with fixes (of course some things may still get added, but if your not carful you just end up in a loop of despair)
There are also addon considerations, which ones are you running just so I can make sure to give them a test. I'm pretty sure there will be a few breaking issues.
The update script is there but I have not done the needed testing. That script is really concerned with db updates, so I need to do a fresh 118 -> update to 20 and then do some comparisons. The other update issue/question/decision is that the file structure really changed under 2.0, its now follows PSR guidelines, so I need to make sure the upgrader cleans up after itself.
I pushed a couple of large updates to the repo but they are not live here just yet. I also have a couple of smaller features I was thinking of adding and a few areas to simplify. I also want to pack up 1.1.9 so were are better prepared for 8.1
So maybe wait several more weeks so we can get a few more things done :grin:
Word. Thanks for the advisement @Spuds
It's no rush nor critique, to be clear. One site has a crew offering unique if not creative ways to break things. They also provide constructive feedback when they do. Thus it's a reasonable testing grounds.
Anywho, we'll patiently await further updates!
Oh, one other question. Will custom css be reasonably close in 2.0, or will a 1.8 custom css require substantial overhaul?
Perhaps it's also pertinent to expand the question. Will there be substantial theming changes in 2.0, or can 1.9ish themes be ported with reasonable ease?
I think what I need to do is take one of my 1.1 themes and see what is required in order to make a fully useful response. Its going to be very theme dependent with respect to what was changed/adjusted.
A custom.css only theme should mostly just work. I don't recall any major CSS selector changes, so whatever was being targeted by the custom CSS should still be available. That said, structurally many things were moved to grid and flexbox, as such how you adjust items may not be the same. For example the old board index was div/span/float/margin in structure and now its grid-template-columns: [bicon] 75px [info] auto [avatar] 60px [latest] 32% [stats] minmax(80px, 120px) [end]; Which may look complicated but its really not, and you can rearrange and delete the items with ease.
Themes with custom templates will need some effort, mostly if you want to take advantage of the new features, such as the improved metadata (note I did add that in 1.1.9, but to use it with a custom theme, its index.template would need to be updated to output the data, the updater should offer this but ...) Custom themes likely have their own board/message/display templates with their own css, which again should "work" But things such as who liked a post, that was hidden until you did a button hover (poor accessibility) is now shown by default.
Font awesome support was removed in 2.0, but could easily be added back with a custom theme. It was depreciated in 1.1 and not used by the core theme.
The top menu is now pure CSS, removing hoverintent/superfish js from use. So themes that did very custom menus, or used those JS functions to adjust fade in/out would need some changes. Part two of that change is when you use click menus, such as mobile/touch devices, that is still JS (new code) enabled, so you would want to test changes both ways.
Font size changed slightly, but most importantly the way its done now stops a lot of the compounding effect that we had, so a custom theme may find some of their font sizes will need to be adjusted.
Other menus were also changed/simplified made consistent, so again depending on what you did ....
I could go on, but I feel most adjustments should be straight forward as the overall look did not really change, but many of the old ways of doing it were changed. I know that is not much help :sad:
Don't worry! The most important thing is that an update to 2.0 goes through without problems. The theme with its variants in dev 2.0 is top-notch! :thumbsup:
What are the plans for Elkarte 2.0.0.
I can see there are 169 open issues against it, however looking at them from an outsiders point of view. I think many can be closed down as not required now or supeceeded. I'm more asking from an addon development point of view as I have just updated TinyPortal again to work with 2.0.0 and was going to work my way through the other addon's I have, but if there are going to be drastic changes (like the changes to how language txt files are loaded as that broke my logic and I had to implement my own loader) it makes sense to hold fire.
There should not be any more core changes like what we did with the language files, at least I am not planning on any at this point.
Agree many of those issues can simply be closed. I started to go through them a few months ago and did the work of fixing/adding or closing them. There are a lot that simply kept being pushed to the next release, some are valid improvements and could be moved to projects, should someone want to take them on, but the majority are old crust.
On the language issue you faced, if there is a helper function or logic change that could be added to the core, let us know!
I've been stuck on 1.1.9 (I keep saying its close and then, another little issue shows up), so have not been able to work on 2.0 in a couple of months. Should be able to get back to it soon :pray:
Is this version available now?
Not really. All of the code is available in the Github repo, but I don't think the install is working.
I have fixed several issues, including install problems, but have not pushed the updates to the repo (yet). Unfortunately 1.1.9 has been sucking the life out of me.
I can tell you that the latest released patch runs fine. Even with php 8.2.
Awesome to hear ... Honestly every time I think 1.1.9 is done and I package it up, do some patch/install tests/etc, another little issue shows up :zany_face:
Just packed it up already and leave the fixes via forum post which will be compiled later in 1.1.10, if any. For now, focus on 2.0 is better.
Just did a site update to the latest 2.0 code.
Honestly don't remember exactly everything that changed as these were updates and fixes that were in flight as I was trying to get 1.1.9 out the door. In any case there were a bunch of bug fixes that I did over the last few months as well as 1.1.9 fixes that were also needed in 2.0.
As always clear that cache. Next update I'll try to remember to add the cache stale string so everyone does not have to manually flush the cache.
So lets see what we broke this time :tongue:
Did another small bump of the site files ....
Fix for likes not working on button click
Fix for Quote on collapsed QR not working
PM from was missing when in conversation view
Various theme tweaks
Unapproved attachments fixes
Edit all option in board profiles was broken
Lot of formatting / psr / cleanup / docblock stuff
Add fast CSS compression with a whitespace/comment stripper
Update chart.js to latest, fix stats layout, fix stats errors for removed members
Many other minor fixes