Project

General

Profile

Actions

Bug #17298

closed

Frontend preview and simulate time is buggy

Added by Michael Stucki almost 17 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Should have
Category:
Communication
Target version:
-
Start date:
2007-05-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.1
PHP Version:
4.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

It seems like preview time is not respected correctly. As soon as it is set, all content is displayed disregarding any start- and enddates.

How to reproduce:
Edit a page and add some content with a startdate in the future.
Next, open the admin panel and simulate a date which is earlier than the startdate set above. The content will always appear disregarding of the setting.
(issue imported from #M5611)


Files

bug_5611.diff (2.68 KB) bug_5611.diff Administrator Admin, 2007-05-11 13:43
5611_trunk_4.3.patch (2.69 KB) 5611_trunk_4.3.patch Administrator Admin, 2008-11-01 12:10
5611_4.1.patch (2.68 KB) 5611_4.1.patch Administrator Admin, 2008-11-01 12:26
5611_4.2.patch (2.69 KB) 5611_4.2.patch Administrator Admin, 2008-11-01 12:26

Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #19544: Time simulation in Frontend PreviewClosed2008-10-31

Actions
Related to TYPO3 Core - Bug #20524: Hide on FE-login still shows elemens in simulation modeClosed2009-05-29

Actions
Has duplicate TYPO3 Core - Bug #17384: simulate Backend Group shows always hidden pages and recordsClosedMichael Stucki2007-06-13

Actions
Actions #1

Updated by Michael Stucki almost 17 years ago

It seems like sys_page->versioningPreview is set as soon as $TSFE->fePreview is true. However, fePreview is not the same like a versioning preview. Therefore, the check must be changed.

I'm not sure how to assure if we are in versioningPreview mode, but I assume that one of these needs to be set:
- t3lib_div::_GP('ADMCMD_view')
- intval($TSFE->workspacePreview)

That should also cover any versioning preview links (ADMCMD_prev)...

Actions #2

Updated by Ralf Hettinger almost 17 years ago

Does work for me. Thank you.

Actions #3

Updated by Andreas Kiessling about 16 years ago

I just encountered this error in current 4.1.5 and was able to fix it with this patch. So this patch wasn't implemented in 4.1.5?

Actions #4

Updated by Martin Holtz about 16 years ago

seems to be an duplicate bug of #7320 too

Actions #5

Updated by Ralf Hettinger about 16 years ago

Any chance of getting this into 4.2?

Would really make a new setup much easier ;)

Actions #6

Updated by Ralf Hettinger almost 16 years ago

Any objections against putting this to the core list for 4.2.1?

Actions #7

Updated by Sven Weiss over 15 years ago

Isn't in 4.2.2 and not in the actual trunk of v4.
Can someone apply this for the next release / tag?

Actions #8

Updated by Sebastian Verweyen over 15 years ago

When will it make it's way into a release build?

Actions #9

Updated by Ralf Hettinger over 15 years ago

"When will it make it's way into a release build?"

That's what I'm wondering myself, so I submitted patches against the current svn branches to the core list.

Actions #10

Updated by Michael Stucki over 15 years ago

Fixed in TYPO3 4.2.3 and later.

Actions

Also available in: Atom PDF