Newscoop 4.1 has been released and includes frontend search capabilities powered by Solr, the open source enterprise search platform used by Netflix, Instagram, SourceForge, NASA, WhiteHouse.gov and Apple.
There is also a critical security fix meaning upgrade is strongly recommended.
Solr is an open source enterprise search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting, faceted search, dynamic clustering, database integration, and rich document (e.g., Word, PDF) handling. Providing distributed search and index replication, Solr is highly scalable.
- Integration of Apache Lucene Solr - New article-rating feature allows readers to give a rating feedback to the author which can optionally be displayed on the frontend - New Facebook Login allows journalists and editors to sign in to site backend with Facebook logins - New tags for the template engine: list_users and list_user_topics - Security fix: Unnecessary error reporting exposed on front-end templates - 11 other important bug fixes
Congratulations to the whole Newscoop team and huge thanks to all the Georgian organisations who helped us with this, plus to everyone who bug-tested and gave us feedback.
It was tested in different platforms before releasing. Can you please provide more details on the platform and settings you are running the installation on? Thanks.
I did a full backup and removed all DocumentRoot content.
I got 4.1 version from github, unzipped it, copied the newscoop folder's content into the DocumentRoot on OpenShift (same things i did with 4.0.3) and, when accessing my url, while expecting the install process, i get a blank page.
PHP Version 5.3.3, MySQL 5.1, running on Linux ex-std-node110.prod.rhcloud.com 2.6.32-279.14.1.el6.x86_64 #1 SMP Mon Oct 15 13:44:51 EDT 2012 x86_64.
The changelog headlines are as follows: - New article-rating feature allows readers to give a rating feedback to the author which can optionally be displayed on the frontend
- New Facebook Login allows journalists and editors to sign in to site backend with Facebook logins
- New tags for the template engine: list_users and list_user_topics
Where we can find documentation on these three changes?
hello Andrey. Isn't sure this depend from cache, because i tried open link from another computer. I never open before there sourcefabric resources. There i see 4.0.3.tar.gz Anyway, I cleared cache on my pc and tried again to download archive from sourceforge and got newscoop 4.0.3 Look at screenshot please, why green button have 4.0.3 caption?
My main browser is FF 18.0.1, but i tried download via chrome.
Strange behaviour. I just checked it out using couple different browsers and the green button reads "Newscoop 4.1.0" and the link you provided to latest available file gets me newscoop-4.1.0.zip
Hi Holman. I do not understand anything. I connected to home pc via teamviewer and tried to download archive and got newscoop_4.0.3.tar.gz. Then Iasked a friendwho worksas network administrator andlives in another city, downloadthe archivehere.He alsogot4.0.3. Then I click Browse all Files i see all versions, including 4.1.0, but nevertheless,at the topis listed as4.0.3finalversion.
Hi Martin. I'm not sure about different servers, but ofcource SF have many servers, anyway content should be mirrored. My provider have cache-server but it is transparent. Atwork Iadministerthe serveris responsible for accessto the Internet andto be sureto clear the cachethere, butthe resultisnot produced. I live in Ukraine, this is not so far from You and I write about what i see. Perhapsit is a problemwith the cacheserversand maybe not.I do not knowwhat to think,everything in my powerI did.
Post edited by Ruslan Shilov at 2013-01-31 06:39:43
Could be a problem with the 'recommended version' button of SourceForge. I'll double check the latest version is recommended for all users, all locations, all OSs.
Hi all Andhere is the solutionof the problem.Idid not do anything, justwait.Refresh the page andseethe buttonto download the4.1.0, the sameversion of theproposed
Very sorry about this, was an oversight in our usual release day workflow. We'll double check this next time. We had actually spotted it internally, but thought it was caching and didn't follow up.