In previous versions, there was no message if no search results were found in any module - just the search form. I agree it isn't the best user experience and should be addressed, but that wasn't the purpose of the 1.3.5 release.
Now, I do see an error in the changes made to the search in regards to modules with no results - the logic is backwards in the current packages. This needs to be fixed before we release - 1 simple ! will take care of this.
In testing to confirm this, I have discovered that if no module has any results, the page is just as Rene describes it above - no message, no modules shown with 0 results - just the form. Basically, the option to display modules with no search results only works if at least 1 module has a result. I haven't found the fix for this, yet.
is that different in 1.3.4?
I tested the last final pack and I think we have an issue in the search result page. If you enter a keyword who is not available, you get a redirect to search page, but no information that the page could not find anything. This is very confuse for the user
The release of 1.3.5 final will not be delayed by the changes to the documentation headers for copyright information, nor will it require another RC release. We have addressed this in the past.
We are still on track to release the final this weekend, along with an updated 1.2.8 (Smarty update for security).
Anyone can hear my? :)
Please commit the latest files to 1.3.6,since we have codefreez. We waiting for the final version soon.
Tested again and think, we can go final now. Well, the copyright thing can be done before.
We received a mail from the xps project that some copyright info is still missing. I'd like to check that prior to releasing a final. Final was scheduled for release on the 31st anyhow. My verifications will be done before that.
I think too, we are ready
Hello, all - ready for the final?
someone needs to keep a close eye on me - commit 12261 did not apply to 1.3 (though it does still work).
If it all works - we can tidy up for final.
Thank you for the updated files @fiammybe - btw, I tested an update also and it looks good for me.
@sato-san I came to the conclusion that the files that I created didn't include Steve's last 2 commits. I've added the changes into the RC2 branch now,
I'll create the files in the evening, and they will be uploaded immediately after that.
Sorry for the delay.
I tested also, but incl the last 2 commits from the branch. And it's works as well for me with a fresh installation.
thanks qm-b. I'm uploading the packages at the moment.
Thanks for whole work, David. Tested around the fixes in core and modules. Seems to be much better now. This will be a very nice update
I just created the files for the release of ImpressCMS 1.3.5 RC2. Please have a quick look and test. If I don't get any negative notifications by tomorrow (well, that's more or less 14h from now), I'll publish the packages and the news.
these packages now include RC versions of content and profile, to include the improvements that have been made.
yep, that's a feature request, not a bug report
Ok, well - put in a feature request I guess. I don't really see what is difficult about using fieldsets and css though. And bootstrap is at the core of the system now... sooooooo.....
I see what you mean, but actually my admin is totally different from the core one because I think we could make it more modern looking not only in visual but also in features for newbies or not so technical users.
One thing I'd like to see is that we could be able to produce more flexible form layouts by adding a new param that would allow us to reposition the form fields in a grouped way or slimpy allowing to have two fields side-by-side or even being able to create categories in news in an ajaxed approach.
I know how to do it but if this could be a core feature it would help many others, maybe not so good coders, that could generate simpler modules through imbuilding.
After having built over 50 commercial modules to tailored solutions I think this could be a nice add-on.