I updateted to the latest tx_news Version 9.0. Since the ViewHelper <n:widget.paginate> are no longer supported as of TYPO3 11, I have changed the pagination template as recommended. Unfortunately, so the setting of the maximum links no longer works: settings.list.paginate.maximumNumberOfLinks = XYZ Is there a workaround for this?
Screenshot of cropped pagination
Thanks and best regards
Michael
If you want to use settings.list.paginate.maximumNumberOfLinks, class GeorgRinger\NumberedPagination\NumberedPagination is required.
You can use the following extension (beta) by Georg Ringer:
https://extensions.typo3.org/extension/numbered_pagination
Related
We are adding version in the url for making our application backward compatible.
We have an url version: {mysite}.com/v1/author/id
May be in the next version of the app we may use something like this - {mysite}.com/v2/contributors/author/id
In order to support old url format in the new app, we are adding version in the url. By using the version in the path, we will know the url format and handle accordingly.
Is this the best way to do this or is there any other recommend approach for this?
I prefer React Router(Navigate to specific file/folders) on the version differentiation , if your both version is managed in same repository.
I've noticed that when using Jxbrowser's default print dialog (using JxBrowser version 6.7) and printing a document with many pages, the page selection only goes up to 100 pages.
When you type in more than 100, it reverts back to the previously set number and you can't increment to more than 100.
Is this just me?
I am here to inform you that we’ve just released JxBrowser 6.14 where the mentioned issue has been resolved.
This version is available for downloading at https://www.teamdev.com/jxbrowser
I'm writing you to let you know that the issue has been fixed. You can download EAP build with the fix from https://storage.googleapis.com/cloud.teamdev.com/downloads/jxbrowser/eap/jxbrowser-6.14-b13-eap-cross-desktop-win_mac_linux.zip
The fix will be included in official 6.14 release probably this month.
This video is showing how to embed tweets in umbraco 7. In the current version it does not seem to work anymore. When I try to do it I get the error message "not supported".
Is there anything additionally to do to get this working? Any additional packages?
I think that feature uses OEMBED, it's possible that Twitter have updated their API and the functionality is broken. I'd log an issue on the Umbraco Issue logger: http://issues.umbraco.org so that the core dev are aware of the issue and can investigate further.
Could also try this package https://our.umbraco.org/projects/website-utilities/utwit/ , have used it before and works perfect but haven't tried it on v7 yet but it says it work and i trust Matt (the guy that made it big umbraco dev and contributor) so should work.
Latest version of SDWebImage allows app to override its rigorous caching mechanism and honor HTTP Cache headers with this flag - SDWebImageRefreshCached but its not available in older versions. Is it possible to do the same with older version 2.7.4?
Thx
This is not really an answer to the question but it did solve my problem. Looking more into the code I found that the images are not cached for ever. The api uses maxCacheAge to expire the cache and clear the images and this is set to 1 week by default. In 2.7.4 this value can not be modified but I believe it can be in later versions. in case this helps someone.
static NSInteger cacheMaxCacheAge = 60*60*24*7; // 1 week
I am using wkhtmltopdf to generate reports from my html templates, i am trying to generate an index for the output PDF.
The thing is that I want to achieve similar functionality to the indexes of microsoft word.
For this purpose I need to use several internal links among the document, so when clicking in the index of the PDF, it goes to page 10 for example.
Any clues about how to achieve this?
I am using wkhtmltopdf version 0.11.0 rc2 in Windows, but sooner or later I will have to move it to linux so I need a compatible solution among operating systems.
Thanks a lot in advance.
I got the solution by my self, but i just haven't check compatibility with Linux.
For achieving the internal links you add in the html:
Target of the Link:
<a name="name_of_target">Content</a>
Link to the Target:
Link Text
It works perfectly when converted to pdf.
It can be tricky. E.g. invisible (empty) links don't work as targets. Also, the structure seems to matter and not all valid html5 layouts work. E.g. I found that while this works:
<h2><a name="name_of_target">Target</a></h2>
this does not:
<a name="name_of_target"><h2>Target</h2></a>
Despite both being perfectly valid (in html5). (I'm using version 0.12.6.)
I had the same issue with wkhtmltopdf
wkhtmltopdf 0.12.2.1 (with patched qt)
with debian 9 installed with the package.
wkhtmltox-0.12.2.1_linux-jessie-amd64.deb
I enabled the internal links with the command option
--enable-internal-links
I used the target:
<a name="name_of_target"><div><img src="image.png">Content</div></a>
and the link
Link Text
But still not working, other link in the document worked well.
Then I replaced the div with a span and it worked.
<a name="name_of_target"><span><img src="image.png">Content</span></a>
The issue is related with the display block rule of div elements. When I added display block rule to the span the link not worked again.