Page 1 of 1

[Solved] Issue with {news} after upgrade to 1.12

Posted: Mon Apr 27, 2015 7:49 pm
by pwg
Hi,
I recently upgraded a site to version 1.12, and am now having an odd issue with the New module. I can't seem to set it to display only one article. It was fine prior to the upgrade.

Trying both (and combined) {news pagelimit="1"} or {news number="1"} both display 2 news stories.

If I use {news pagelimit="x"} x number of articles are displayed - it seems to only be when I want just the one article, that there is an issue.

Anyone else spotted this?

Am I missing something obvious?

Thanks for any help.

Copied system info - just in-case.
Cms Version: 1.12

Installed Modules:

CMSMailer: 5.2.2
CMSPrinting: 1.0.5
FileManager: 1.4.5
MenuManager: 1.8.6
MicroTiny: 1.2.9
ModuleManager: 1.5.8
News: 2.15.1
Search: 1.7.12
ThemeManager: 1.1.8
CGExtensions: 1.45
JQueryTools: 1.3.4
CGSmartImage: 1.17.1
CGSimpleSmarty: 1.7.4
CGBlog: 1.12.9
CGGoogleMaps2: 0.99.1
FormBuilder: 0.8.1.1
GBFilePicker: 1.3.3
Gallery: 2.0.1
ECB: 1.6
CGFeedMaker: 1.0.20
Disqus: 2.0
AceEditor: 1.0
Banners: 2.7
FrontEndUsers: 1.26
SelfRegistration: 1.8.3

Config Information:

php_memory_limit:
process_whole_template:
max_upload_size: 128000000
url_rewriting: mod_rewrite
page_extension:
query_var: page
image_manipulation_prog: GD
auto_alias_content: true
locale:
default_encoding: utf-8
admin_encoding: utf-8
set_names: true

Php Information:

phpversion: 5.5.23
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
E_STRICT: 2048
E_DEPRECATED: 8192
memory_limit: 256M
max_execution_time: 300
output_buffering: 4096
safe_mode: Off (False)
file_uploads: On (True)
post_max_size: 128M
upload_max_filesize: 128M
session_save_path: /tmp (0700)
session_use_cookies: On (True)
xml_function: On (True)
xmlreader_class: On (True)

Server Information:

Server Api: cgi-fcgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.5.34
Server Db Grants: Found a "GRANT ALL" statement that appears to be suitable
Server Time Diff: No filesystem time difference found

Cheers,

Paul

Re: Issue with {news} after upgrade to 1.12

Posted: Mon Apr 27, 2015 10:04 pm
by Dr.CSS
Maybe the {tag} needs to be in uppercase..?

Re: Issue with {news} after upgrade to 1.12

Posted: Tue Apr 28, 2015 1:20 am
by pwg
Thanks Dr, and worth a shot, but I'm afraid not, using {News pagelimit="1"} gives the same behaviour, that is publishes 2 articles.

Cheers,

Paul

Re: Issue with {news} after upgrade to 1.12

Posted: Tue Apr 28, 2015 9:18 am
by velden
Confirm. It's either a bug or done on purpose :)

From the source:

Code: Select all

$pagelimit = max(2,min(1000,$pagelimit)); // maximum of 1000 entries.

Re: Issue with {news} after upgrade to 1.12

Posted: Tue Apr 28, 2015 10:42 am
by jce76350

Re: [Solved] Issue with {news} after upgrade to 1.12

Posted: Wed Apr 29, 2015 12:22 am
by pwg
Many thanks again Velden, and jce76350.

I've added solved to the title, and modified my News/action-default.php page code as workaround till a fix is published.

Cheers,

Paul