Easter holidays, so work has been a bit more slow. I did manage to finish the German translation in transifex this evening, I'll upload a complete translation pack tomorrow.
I did start to rework my solution to plugin to the composer library, but I got lost in the complexity of what I'm trying to get. I think I'm aiming too high, certainly for a first version Work continues on that, because it is one of the remaining new funtionalities that needs to go in before we can start looking into producing beta versions of the 2.0 branch - feature complete, but perhaps more bugfixing needed. My new approach is to let the design patterns on the side for the moment, and just get something working first. We can refactor the hell out of it afterwards.
Because nobody understood why we work in the 'retro' branch, and because those reasons date way back, Mekdrop has taken on the task of migrating our working branch for ImpressCMS 2.0 to the 'master' branch.
I have already come across Tom Butler's articles (hard to forget him, with his exuberant hairstyle profile photo ) and he has some very interesting points, yes. I admit I'm also no rockstar developer in PHP to be able to follow the entire reasoning in 1 go. Some kind of url routing would be interesting to have in ImpressCMS2 (2.0 or a later iteration), for a start.
I've been looking into the MVC pattern, and came across a programming blog that has some very interesting articles about MVC and a couple of its descendants - MVVM and MVVMC. Also has some cool stuff about how to build a front end controller to handle routing.
It took me a few reads to get my head around it. I thought I had been doing MVC, but it turns out not in a very strict sense. Anyway, I'm trying to build something using a front controller and the MVVMC pattern, which is basically MVC except the view gets split into two components (a view plus a 'viewmodel') to decouple the view from the model and allow each component to be substituted or re-used. Together with the front end controller/router it gives you a lot of flexibility.
Worth a read if you have time (see the section 'MVC Related Articles').
I did a similar move more or less a year ago when we migrated the ImpressCMS site from multiple versions to 1.3. Some modules were no longer available in 1.3, so we had to reconfigure everything from scratch, and we also did a few SQL-based custom written migrations.
As far as I know, no module out there has 'import' functionality so you might need to write your converters on your own. Having a framework (à la Drupal Migrate) that offers a standard way of doing this would be a major positive point for a future version I believe.
Moving from CBB to iForum is easy : the table structure is the same, and the URL structure is the same. If you move the attachment files into the iForum upload folder, you should be OK.
I've installed the Chromium-based Edge browser on my machine, and it works like a charm. I know people will look at me sideways when I say that I didn't have any problem with the Edge that was included in Windows 10, I'm generally not such a plugin user so their initial lack didn't pose a problem to me. The chromium-based Edge feels faster and more responsive, and it remains very much Edge. The fact that there's a Google-sponsored Chromium engine underneath hasn't changed that much.
I mention this because I tested our site (of course) with Chromium Edge, and noticed that Edge now also suffers from ticket #100 in ImpressCMS 1.3. Time to get that sorted out.
David L asked how he could test out or current state of ImpressCMS 2.0, and it turns out that the documentation for that is severely lacking and/or out-of-date. I've given him a short roadmap on how to get a ImpressCMS 2.0 alpha 7 site up and running on his shared hosting, but it's time I wrote some documentation.
I discovered this morning when I was on the train going to Brussels that my work on the composer integration was more or less useless because I was re-inventing the wheel. Composer has a class 'installer' that takes care of most things for me.
I'm looking into resurrecting the API documentation for 1.3 and 2.0, and I've looked into Fabien Potencier's SAMI to do so. I know, it's been discontinued, but I still have to find a tool that allows me to do a command-line crawl directly in my Github repository. I have some issues with git telling me that my repository is not clean in the 1.3 branches, so I'll need to do some spring cleaning before that can be published.
I'm starting this thread to give you an idea about what I'm currently working on, without needing to fire up another module or another external service to do so. No guarantees about the frequency though.
No guarantees about the content either, except that it will be ImpressCMS-related, but I might ot limit my contributions here to pure development aspects.
I do use group permissions for news categories - not everyone can see every category of news. The same is true of the forum, as well. Being able to assign permissions based on group and category is pretty crucial in a lot of sites, IMO.
Modules that were built on the newer code base of ImpressCMS don't seem to have this feature - or am I wrong? I am also wondering about migrating data - do the modules account for the move from old code base to the new code base, or will I be working out my own data migration?
Also - has anyone gone from 1.2.x to the latest 1.3.x? Are there midpoints that are best handled in steps?
I've started looking at the translations again. ImpressCMS prides itself as a multilingual CMS, that means at least that people can expect to find the user interface in their native tongue. We still have some improvements there
At the current state of things, 3 languages are fully complete : English (duh), French and Dutch. Several others are nearing 100%, such as Korean, Spanish, German and Italian. With a small amount of effort, we could get to 7 languages 100% complete in the near future.
If you are interested to participate in these languages, or know someone who is, Transifex is the site to go to. If you want to improve or add another language, please don't hesitate and let me know, either here or on Transifex
I noticed when looking for the autocomplete code from some time ago, that the link went into the void. At first, I was afraid that the files didn't get migrated during one of the multiple moves we did from Inbox > Siteground > Other siteground account > unified site.
Nothing so dramatic: as it happens we migrated from newbb to iforum as forum module on that last account, and the files were still in the newbb upload folder.
I moved the files, and the links I tested worked out for now. I hope this makes finding stuff on the forum easier now.
I will be attending Laracon EU Madrid (and possibly also Laracon EU Amsterdam) this year. I wanted to take those opportunities for some marketing in PHP development circles and I'm looking for cool stuff to leave lying around for people to pick up and come look at the project.
I seem to remember there was a cafepress shop somewhere previously, but when i look for Impresscms on there, I get no results.
Do you know of any online shops that have cool swag that we can brand with ImpressCMS?
I'm just testing the stuff to see if I can get another error that kicks in on the forums. I hope it doesn't, that will mean I've fixed the case for the version that we are using on the site.
Perhaps later we'll see into rewriting the forum module more thoroughly.
Visibly the fix wasn't working as I thought. It's a difficult fix because the problems isn't there the entire time
When you look at the error message, there is an error in the SQL because one of the keys in the object seems to give a totally nonexistent value. I tried to fix it now in the old Art framework, but I'm not sure if my fix is working ok. Let's test