Recent Posts
1
The Pub / Re: Wedge&PHP 7
« on December 24th, 2022, 11:42 AM by Nao »How about PHP 8.1?
Okay sorry, haven't visited this place in a while :ph34r:
3
The Pub / Re: Wedge&PHP 7
« on October 7th, 2021, 07:32 PM by Kian »Désolé Kianouch, je ne sais pas à quoi correspond ton problème... Je pourrais débugguer sur ton serveur mais je ne passe pas tous les jours ici... Genre tu pourrais m'écrire, aussi. :P
3 ans après, je me suis repenché sur la question car je souhaite vraiment me débarrasser de cette bécane chez OVH.
J'ai fait cette fois un import table par table et ai pu isoler celle qui pose problème : la table wedge_settings
J'ai beaucoup "joué" avec sans trouver le paramètre qui fait ça, du coup j'ai testé tout simplement en important un dump de tout sauf cette table et tout va bien, je vais donc pouvoir migrer :cool:
Bon me reste un dernier soucis moins gênant mais non lié à PHP 7 : j'ai la plupart des plugins qui ne s'activent pas, quand je clique sur le bouton il ne se passe rien, et ce sur mon vieux serveur PHP 5 comme le nouveau. J'ai du faire une connerie un jour :^^;:
4
Off-topic / Re: My Journey with Wedge.
« on April 30th, 2021, 05:07 AM by Wanchope »Honestly, I haven't the faintest idea about the current state of SMF.
Had I been forced to guess, I'd have said they were advancing at their own speed (i.e. a turtle?), which after all is the reason why I left the SMF dev team to focus on forking it.
Then again, SMF was born around 2003 or so, and it made a lot of progress in 7 years. While it's natural to understand it wouldn't move at a higher pace in the following 10 years (80% of what's need in a forum was already implemented, what else could be done that's not in Wedge already?), it's a bit of a let-down if it's true they haven't done much progress.
ElkArte is a very heavy modification of SMF. It however focused on different areas and isn't really following the same philosophy as Wedge.
Then again their forum also seems to be more active than mine. But obviously it doesn't automatically mean they're advancing faster.
Also, they really need a designer to help with their forum layout, ahah.
I don't consider myself a designer, but my work on the main Wedge theme, I consider better than what Elk and SMF both did. I really wouldn't mind if I found some of it in their software. Come on, even the little details I focused on back in the day, such as doing some JavaScript magic to have user mini-profiles align along their long posts vertically, now that's done with standard CSS -- in this case, position: sticky does the trick.
Anyway. I'm not here to judge anyone. None of us at Wedge, Elk and SMF make money over our work, as far as I know. It's always a passion project. That all 3 of them are still active 10 years after is a testament to how committed we all are.
SMF has not made a single progress for close to 10 years now, unless you mean invincible progress.
If they are not up in being free why not made it paid software and join the market properly?
For goodness sake even phpbb is fully responsive. Nothing to worry about though, serious forum owners will opt to pay for the likes of Xenforo anyway.
5
Off-topic / Re: My Journey with Wedge.
« on April 24th, 2021, 11:04 AM by Nao »Honestly, I haven't the faintest idea about the current state of SMF.
Had I been forced to guess, I'd have said they were advancing at their own speed (i.e. a turtle?), which after all is the reason why I left the SMF dev team to focus on forking it.
Then again, SMF was born around 2003 or so, and it made a lot of progress in 7 years. While it's natural to understand it wouldn't move at a higher pace in the following 10 years (80% of what's need in a forum was already implemented, what else could be done that's not in Wedge already?), it's a bit of a let-down if it's true they haven't done much progress.
ElkArte is a very heavy modification of SMF. It however focused on different areas and isn't really following the same philosophy as Wedge.
Then again their forum also seems to be more active than mine. But obviously it doesn't automatically mean they're advancing faster.
Also, they really need a designer to help with their forum layout, ahah.
I don't consider myself a designer, but my work on the main Wedge theme, I consider better than what Elk and SMF both did. I really wouldn't mind if I found some of it in their software. Come on, even the little details I focused on back in the day, such as doing some JavaScript magic to have user mini-profiles align along their long posts vertically, now that's done with standard CSS -- in this case, position: sticky does the trick.
Anyway. I'm not here to judge anyone. None of us at Wedge, Elk and SMF make money over our work, as far as I know. It's always a passion project. That all 3 of them are still active 10 years after is a testament to how committed we all are.
Had I been forced to guess, I'd have said they were advancing at their own speed (i.e. a turtle?), which after all is the reason why I left the SMF dev team to focus on forking it.
Then again, SMF was born around 2003 or so, and it made a lot of progress in 7 years. While it's natural to understand it wouldn't move at a higher pace in the following 10 years (80% of what's need in a forum was already implemented, what else could be done that's not in Wedge already?), it's a bit of a let-down if it's true they haven't done much progress.
ElkArte is a very heavy modification of SMF. It however focused on different areas and isn't really following the same philosophy as Wedge.
Then again their forum also seems to be more active than mine. But obviously it doesn't automatically mean they're advancing faster.
Also, they really need a designer to help with their forum layout, ahah.
I don't consider myself a designer, but my work on the main Wedge theme, I consider better than what Elk and SMF both did. I really wouldn't mind if I found some of it in their software. Come on, even the little details I focused on back in the day, such as doing some JavaScript magic to have user mini-profiles align along their long posts vertically, now that's done with standard CSS -- in this case, position: sticky does the trick.
Anyway. I'm not here to judge anyone. None of us at Wedge, Elk and SMF make money over our work, as far as I know. It's always a passion project. That all 3 of them are still active 10 years after is a testament to how committed we all are.
6
Off-topic / Re: My Journey with Wedge.
« on April 22nd, 2021, 05:27 AM by Wanchope »I hereby give permission to the SMF team to backport anything they like from Wedge into SMF, as long as they follow the BSD licence guidelines. Same for ElkArte and its team.
The other one you mentioned here seems like a typical smf 2.1 changed from blue to green colour and then a rather confusing menu icons (very annoying on mobile) in place of simplified text, ie, to non developers anyway.
7
Features / Re: New revs
« on March 27th, 2021, 06:40 PM by Nao »[Commit revision 750c3a6]
Author: Nao
Date: Sat, 27 Mar 2021 18:40:17 +0100
Stats: 1 file changed; +4 (insertions), -1 (deletion)
Date: Sat, 27 Mar 2021 18:40:17 +0100
Stats: 1 file changed; +4 (insertions), -1 (deletion)
- The :where() automation code worked fine, but the world may not be ready for it, so I'm removing it for now. It might break some existing CSS, hopefully it won't be worse than what :where() used to break. (Subs-Cache.php)
- Full explanation: https://wedge.org/pub/feats/6108/new-revs/msg297990/#msg297990
8
Features / Re: New revs
« on March 27th, 2021, 06:36 PM by Nao »Well, regarding the :where, it threw problems at me. Specifically, notifications stopped working on my other website because I have an extra class that uses the .notifs base, and it just shows that the standard isn't really ready for automation.
Code: [Select]
I could modify my .mimenu declaration to not be 'final', so that .otherclass also reuses it, and then it'd probably work. Or I could specifically prevent that class that being converted into a :where() or whatver. But this just proves to me that there is currently no sure way to make it work at execution time. So I'm disabling it temporarily. Feel free to tell me if you can figure out a way! I loved :where(), but as it is, I'd rather have it work and waste a few bytes in my gzipped file. (Really, it's just that-- a few bytes. Doesn't matter as much in 2021 as it did in the early 2010's when I worked on this feature...)
.notifs .mimenu { opacity: 0 }
.otherclass .open, .notifs .open { opacity: 1 } // This will work
:is(.otherclass, .notifs) .open { opacity: 1 } // This will work
:where(.otherclass, .notifs) .open { opacity: 1 } // This will NOT work!I could modify my .mimenu declaration to not be 'final', so that .otherclass also reuses it, and then it'd probably work. Or I could specifically prevent that class that being converted into a :where() or whatver. But this just proves to me that there is currently no sure way to make it work at execution time. So I'm disabling it temporarily. Feel free to tell me if you can figure out a way! I loved :where(), but as it is, I'd rather have it work and waste a few bytes in my gzipped file. (Really, it's just that-- a few bytes. Doesn't matter as much in 2021 as it did in the early 2010's when I worked on this feature...)
9
Off-topic / Re: My Journey with Wedge.
« on March 23rd, 2021, 03:25 PM by Nao »I've changed the question asked of new users when they attempt to post. I can't really do much about real people posting advertisements, unfortunately. I'm not going to start moderating messages before they even show up on the website. That'd be silly. Anyway...
Also, as you may have noticed, I posted a fix for Firefox today.
I'm still on the lookout for any changes I need to apply to the software. It's not perfect, but I'm still happy with it.
I haven't changed the license yet, but since it'll eventually be done (I'm still hesitating between license types, but it'll be BSD-compatible anyway), I hereby give permission to the SMF team to backport anything they like from Wedge into SMF, as long as they follow the BSD licence guidelines. Same for ElkArte and its team. I don't know of any other 'major' forks of SMF..?
If you want to tell them, you also can. It's a public discussion, as far as I know. ;-)
Also, as you may have noticed, I posted a fix for Firefox today.
I'm still on the lookout for any changes I need to apply to the software. It's not perfect, but I'm still happy with it.
I haven't changed the license yet, but since it'll eventually be done (I'm still hesitating between license types, but it'll be BSD-compatible anyway), I hereby give permission to the SMF team to backport anything they like from Wedge into SMF, as long as they follow the BSD licence guidelines. Same for ElkArte and its team. I don't know of any other 'major' forks of SMF..?
If you want to tell them, you also can. It's a public discussion, as far as I know. ;-)
10
Features / Re: New revs
« on March 23rd, 2021, 03:20 PM by Nao »So, apparently there were some changes internally at github and they deleted the webhook for Wedge. I reinstalled it, and it didn't work. I had to rewrite some parts of the code to allow it to go through. I don't know if anyone's interested in getting the updated code? If no one is, there isn't much of a reason for me to commit the changes (for some reason, my local plugin repo was deleted.)
So, I'm adding manually the two commits that were not posted here, they're both mine and dated from earlier today:
https://github.com/Wedge/wedge/commit/d802a61d455ca56e27fc839e7f92f23c57c988ae (minor AeMe bug I never bothered to fix on the repo before),
https://github.com/Wedge/wedge/commit/b37452eaaa4233ba361b71fc936c4fca28515ce7 (fix for Firefox breaking some CSS due to how :matches is implemented over there, thankfully they have :where now, which works fine everywhere.)
Sadly, I never committed anything in 2020.
Damn year!
So, I'm adding manually the two commits that were not posted here, they're both mine and dated from earlier today:
https://github.com/Wedge/wedge/commit/d802a61d455ca56e27fc839e7f92f23c57c988ae (minor AeMe bug I never bothered to fix on the repo before),
https://github.com/Wedge/wedge/commit/b37452eaaa4233ba361b71fc936c4fca28515ce7 (fix for Firefox breaking some CSS due to how :matches is implemented over there, thankfully they have :where now, which works fine everywhere.)
Sadly, I never committed anything in 2020.
Damn year!