Bug #42558
closed
Content sliding doesn't work when using 'show content from page'
0%
Description
Hi all,
I have a template setup which uses slided content. However, the slided content disappears when configuring a page showing content from another page (on the appearance tab).
I believe this is a bug. Can anyone comment on this?
Victor Oomens
Updated by Thorsten Kahler over 11 years ago
- Category set to TypoScript
- Status changed from New to Needs Feedback
- Priority changed from Must have to Should have
Hi Victor,
on which page did you activate "show content from page"?- current page (i.e. where the slide starts)
- the page that should stop the slide (i.e. where the field ain't empty)
- somewhere in between
Maybe you can provide the relevant part of your TS setup?
Updated by Victor Oomens over 11 years ago
Hi Thorsten,
The page where I applied the 'show content from page' is somewhere in between, because I use infinite sliding.
Here the TS:
lib.featurearea < styles.content.getBorder
lib.featurearea.wrap = <div id="features" class="featured_boxes">|</div>
In the TEMPLATE subparts:
featurearea < lib.featurearea
featurearea.slide = -1
This setup works if show content from page is empty.
Updated by Alexander Opitz almost 11 years ago
- Status changed from Needs Feedback to New
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.2 (Frontend)
- Complexity set to hard
- Is Regression set to No
Updated by Benni Mack almost 9 years ago
- Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Updated by Susanne Moog over 8 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Benni Mack over 2 years ago
- Status changed from New to Needs Feedback
Can you share your tree and site configuration? If you expect to slide from the content where this is shown, I think a Page of type MountPoint is much more useful.
Updated by Riccardo De Contardi over 1 year ago
- Status changed from Needs Feedback to Closed
No feedback since a lot of time => closing this issue.
Plus the ticket is very very old (TYPO3 4.5!!) and would need a new fresh ticket to start working on it
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem on recent TYPO3 versions, please open a new issue with a reference to this one.
As Benni wrote, please add as much information as possible that could help in reproducing your problem
Thank you and best regards