lochmueller / calendarize_news Goto Github PK

See news changelog: https://github.com/georgringer/news/blob/master/Documentation/Misc/Changelog/9-0-0.rst

Using:

• calendarize_news: current master
• calendarize: 11.0.2
• news: 9.0.0
• TYPO3 10.4 latest

Some changes necessary (WIP):

• news: LinkViewHelper now contains typehint must be changed in XCLASS'd VH in calendarize_news

Fatal error: Declaration of HDNET\CalendarizeNews\Xclass\NewsLinkViewHelper::render() must be compatible with GeorgRinger\News\ViewHelpers\LinkViewHelper::render(): ?string in /var/www/t3coredev10x/typo3conf/ext/calendarize_news/Classes/Xclass/NewsLinkViewHelper.php on line 32

Hi,

is there any chance, that the different views (year/month...) could take into account a category assigned to a news-entry.
If I assign a category to a "real" calendarize-event, the category-filtered list-views work as expected. But If I assign the same category to a calendarize-entry with a news-entry (via "Extended"-Tab) the entry it's not showing up in the calendarize-listview limited to this special category.

Everything fine with non-categorized items, either calendarize-items or news-items.

Thanks for infos
Michael

TYPO3 v8.7.24
News v7.2.0
Calendarize v4.1.3
CalendarizeNews v4.1.0

I have a Calendarize List showing Calendarize Events as well as News Events. Details PID points to another page.

This page contains:

1. Calendarize Plugin as Details
2. News Plugin as Details

The links created in the list for calendarize events successfully opens the details page and shows the content.
The links created in the list for news events point to the page the list-plugin is on and not to the details page.

I'm not sure what I am doing wrong here, sorry if this is not an issue but just PEBKAC.

latest release 7.0.0: composer.json

"lochmueller/calendarize": "^10.0||^11.0||^12.0",
"georgringer/news": "^8.5||^9.0"

https://github.com/lochmueller/calendarize_news/blob/7.0.0/composer.json

master: composer.json

"lochmueller/calendarize": "^10.0||^11.0||^12.0",
"georgringer/news": "^8.5||^9.0||^10.0||^11.0"

https://github.com/lochmueller/calendarize_news/blob/master/composer.json

We have been using this for some time with no problems:

"georgringer/news": "^11.1.2",
"lochmueller/calendarize": "^12.4.4",
"lochmueller/calendarize-news": "dev-master"
```,

There is currently no 4.1 package available on composer

The requested package lochmueller/calendarize-news ^4.1 exists as lochmueller/calendarize-news[1.1.0, 1.2.0, 1.3.0, 1.3.1, 2.0.0, dev-master]

I added the constraint dev-master for the time being to add the extension anyway.

If this extension works with calendarize 11, the dependencies could be updated.

News entries that have been calendarized show up in the month, day and list view correctly.
But when I try to open them in the detail view, I get the following error on the detail page: "No Event found! There is no valid fallback PID (list) in the detail plugin".
I can't find a setting for the fallback PID in the plugin.

TYPO3 11.5.27
calendarize 12.4.4
calendarize_news 7.0.0

Will there be a Typo3 11 compatible version of Calendarize News?
Or is it just not tested and I should give it a test drive?

As I am creating a new website I'd really like to go for the all the latest available LTS for the launch.

I am looking for some information on how to configure the ID of the news detail page to be referenced from the list view.

At the moment the link leads to the calendarize list view page itself. That's not what I want.

Any quick hint somebody? Thx in advance!

When calendarize_news is installed, the tx_news option "Manual Sorting" records.manualSorting (boolesch) is not working anymore. No choice to set it in the plugin settings, overwritten by calendarize_news.

ext.table.php line 17 in calendarize_news: $configuration->getManualSorting() is not recognized
$GLOBALS['TYPO3_CONF_VARS']['EXT']['news']['orderByNews'] = 'tstamp,datetime,crdate,title,calendarize';

ext.table.php line 78 in news
$GLOBALS['TYPO3_CONF_VARS']['EXT']['news']['orderByNews'] = 'tstamp,datetime,crdate,title' . ($configuration->getManualSorting() ? ',sorting' : '');

Sorting by event 'start_date' does not work in the news module.

Hi Tim

are there any plans to adapt your extension EXT:calendarize_news with the actual TYPO3 CMS verson 9.5.x with the actual EXT:news 7.x

Thanks for your feedback.

Best regards,
Angelo

Hey Tim, sorry to bother you again.

Without any documentation, I am still very confused about the extension, since I can see there are Xclasses to overwrite the NewsLinkViewhelper and the NewsController->detailAction so the details page should show the date and time from the index, yet it does not.

Also the link to the details page should contain a part &tx_news_pi1[index]={indexId} but it doesn't. This makes it seem like the Xclasses are not being used. I can however find them in the autoload_classmap.php

I think I might still have configured something wrong, so here is my step-by-step:

1. Install calendarize
2. Install calendarize_news
3. Include both static templates
4. Create a folder with some news in them and give them calendarize dates
5. Create and configure the plugins on the respective pages. The list of news-indexes is shown correctly by the calendarize plugin and (after configuring the default details pid for tx_news) links correctly to the details page, though both the link and the details page themselves show no influence of the Xclasses.

Am I missing something important? I love the idea behind calendarize and perfer it massively to calendar_base but only calendarize itself has adequate documentation and I am really struggeling to match calendarize_news to my needs.

Grüße aus Hessen,
Sebastian

I think it was nice, if you a can implement an category selection of existing categories to filter the news-eventlist.

Stephan

Note: This is an error I stumbled on while testing. For me this has no priority.

1. Set the extensions configuration basic.replaceNewsRepositoryByIndexSelection = 0 (default)
2. Create a news element with a calendarize configuration
3. Create a calendarize list plugin configured with storagepid, configurationtype,...
4. Open the list view

Output

(1/1) TYPO3Fluid\Fluid\Core\ViewHelper\Exception

Undeclared arguments passed to ViewHelper GeorgRinger\News\ViewHelpers\LinkViewHelper: index. Valid arguments are: additionalAttributes, data, class, dir, id, lang, style, title, accesskey, tabindex, onclick, newsItem, settings, uriOnly, configuration, content, section
in /var/www/html/vendor/typo3fluid/fluid/src/Core/ViewHelper/AbstractViewHelper.php line 478

at TYPO3Fluid\Fluid\Core\ViewHelper\AbstractViewHelper->validateAdditionalArguments(array('index' => object(TYPO3Fluid\Fluid\Core\Parser\SyntaxTree\RootNode)))
in /var/www/html/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php line 586

at TYPO3Fluid\Fluid\Core\Parser\TemplateParser->parseArguments(' newsItem="{news}" index="{index.uid}" class="pull-left"', object(GeorgRinger\News\ViewHelpers\LinkViewHelper))
in /var/www/html/vendor/typo3fluid/fluid/src/Core/Parser/TemplateParser.php line 353

...

Cause

If replaceNewsRepositoryByIndexSelection = 0 is set, the Xclass of the LinkViewHelper is not loaded.
In this case the index argument of the LinkViewHelper is missing / not defined.

Versions

• Typo3 10.4.16
• calendarize 10.0.0
• calendarize_news 5.0.0

Hi,

The functionality around replaceNewsRepositoryByIndexSelection = 1 is broken.
The classes don't match up their parents definition and won't even load (at least with News v11).

• IndexResult
• NewsController (could be replaced by GeorgRinger\News\Event\NewsDetailActionEvent?)
• NewsRepository

PS: I am not sure what this functionality even does and I have no ambition of fixing it.

For example, if you have calendarize list view and news detail, the URLs will be generated with "extra" index parameter, e.g.

https://mysite/blah/event/my-title-2-5663?tx_news_pi1%5Bindex%5D=58536&cHash=afcc09bda2d3d0729271b2062ae2ce8d

I had this configuration f. news (detail only here):

NewsDetail:
    type: Extbase
    extension: News
    plugin: Pi1
    routes:
      -
        routePath: '/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news
    defaultController: 'News::detail'
    aspects:
      news_title:
        type: PersistedPatternMapper
        tableName: tx_news_domain_model_news
        routeFieldPattern: '^(?P<path_segment>.+)-(?P<uid>\d+)$'
        routeFieldResult: '{path_segment}-{uid}'

I added configuration for calendarize_news:

NewsDetail:
    type: Extbase
    extension: News
    plugin: Pi1
    routes:
      -
        routePath: '/{news_title}'
        _controller: 'News::detail'
        _arguments:
          news_title: news
      - routePath: '/{news_title}/{index}'
        _controller: 'News::detail'
        _arguments:
          news_title: news
          calendarize_index: index
    defaultController: 'News::detail'
    aspects:
      news_title:
        type: PersistedPatternMapper
        tableName: tx_news_domain_model_news
        routeFieldPattern: '^(?P<path_segment>.+)-(?P<uid>\d+)$'
        routeFieldResult: '{path_segment}-{uid}'
      calendarize_index:
        type: PersistedAliasMapper
        tableName: tx_calendarize_domain_model_index
        routeFieldName: slug

Could someone check and confirm?

I think this will be helpful for additional checks for news v9 and TYPO3 v11. I am checking calendarize, how it is done there. In any case, would be nice if checks can be executed via GitHub and locally and with different versions news and TYPO3 (as already done in calendarize, I think).

I could supply a PR but currently not sure how it should be added, several possibilities, can use runTest.sh as well, ....

With replaceNewsRepositoryByIndexSelection enabled how can I control a list view containing news records with multiple index entries?
Flexform fields timeRestriction,timeRestrictionHigh and limit seem not to work here.

Because of the missing dependencies to "calendarize" and "news", the backend crashes after deinstalling calendarize at first.

Hi,
when I change the date of a news-entry afterwards, the different views of calendarize don't change the date...

for example:
I create a news-entry. Date on creation is 01.08. (or whatever I set)
In list- and calendar-news the news-entry is displayed on 01.08. = correct.
If I change the date in the tx-news-entry later, for example to 01.09, the date-field in the calendar-views (and in the backend in the list view of the calendarize-module) is still set to 01.08.
Is this normal behaviour, or did I miss something?

(I already cleared alls caches and ran calendarize:reindex)

Thanks
Michael

Hi Tim

thanks for adapting your EXT:calendarize_news :)

If I install your revised extension i got an fatal error in the backend of my TYPO3 with the following message:

Fatal error: Uncaught Doctrine\DBAL\Driver\Mysqli\MysqliException: Unknown column 'uid' in 'where clause' in /vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/Mysqli/MysqliStatement.php:94 Stack trace: #0 /vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/Mysqli/MysqliConnection.php(120): Doctrine\DBAL\Driver\Mysqli\MysqliStatement->__construct(Object(mysqli), 'SELECT * FROM ...') #1 /vendor/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(844): Doctrine\DBAL\Driver\Mysqli\MysqliConnection->prepare('SELECT * FROM ...') #2 /vendor/doctrine/dbal/lib/Doctrine/DBAL/Query/QueryBuilder.php(206): Doctrine\DBAL\Connection->executeQuery('SELECT * FROM `...', Array, Array) #3 /typo3/sysext/core/Classes/Database/Query/QueryBuilder.php(187): Doctrine\DBAL\Query\QueryBuilder->execute() #4 /vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php on line 71

Any hint?

I do use

TYPO3 version 8.7.23
Composer: No
OS: Linux
PHP version 7.2

EXT:calendarize_news version 4.1.0
EXT:news version 7.1.0
EXT:eventnews (of Georg Ringer) version 3.0.0

Even if i uninstall the EXT:eventnews the error occures. It happens immediately after installing the extension. As soon I click on the Web > Calendarize icon the error occures. If I want to add the plug-In for configure it the whole page can not be opened due to the error. So I got to uninstall the extension to have a chance to edit the page in the be. In the frontend the same error ocures, too.

Best regards,
Angelo