🇺🇸United States @jgoodwill01

Any advances on this feature request? It would be a wonderful module to use but it's limiting in it's current implementation.

Just wanted to see if there was any advances on this image import? Would still love to use Communico Plus on our site but I can't import all the useful information for implementation.

I'm having trouble implementing these updates.

"This release adds Twig templating to the Event and Reservation pages. In addition the entire data available from calls to the Communico API are now available at the theme layer."

Any suggestions on working this theme layer into views and fields for use in display manager? Sorry for my novice but using one of the templates in my theme and applying it to the output for "node--event-page.html.twig" I'm not getting any data but am getting the output fields.

All our other content we run through "Layout Builder" to customize field display is that configurable?

<!-- BEGIN OUTPUT from 'themes/custom/lpl_b4subtheme/templates/communico/node--event-page.html.twig' -->
<h1 class="page-title">
  
</h1>
<h2 class="node__title">
  
</h2>
<div class="c-feature">
  <div class="c-iconimage">
    <img src="" alt="Map pin icon">
  </div>
    <a href="" target="_new"></a>
</div>
<br>
<div class="c-feature">
  <div class="c-iconimage"><img src="" alt="Calendar Icon"></div>
  
</div>
<br>
<div class="c-feature">
  <div class="c-title">Age Group:</div> 
</div>
<br>
<div class="c-feature">
  <div class="c-title">Event Type:</div> 
</div>
<br>
<div class="c-feature">
<a href="" target="_new">
<div id="event-sub-button">Register</div>
</a>
</div>
<p>
  
</p>

<!-- END OUTPUT from 'themes/custom/lpl_b4subtheme/templates/communico/node--event-page.html.twig' -->

Thanks for all your help. Looking forward to getting something functioning and in production one day.

jgoodwill01 → created an issue.

jgoodwill01 → created an issue.

jgoodwill01 → created an issue.

Hi and Thank you,

I've tried two different ways of attaching the block to my Event Pages.

1. Using the template manager for the content type. This works in adding the filters but doesn't pre-populate. It technically functions but isn't great for our application.

2. Using Block layout and assigning to the event page content type, which provides the same functionality as above.

Note: As I was typing this I found that if I remove the "Family Program" type in the popIfEmpty function the communico filter block will prepopulate for us on page load. Not a caching issue we just didn't have that event type.

function popIfEmpty() {
$eventsLimit = '10';
$current_date = date('Y-m-d');
$blockStartDate = $current_date;
$blockEndDate = date('Y-m-d', strtotime($current_date . "+7 days"));
$eventType = 'Family Program'; Change to $eventType = '';

I really like importing the events to our site and I'm getting closer to having that be what we need now that we have a way to filter out private events (by modifying the module).

Providing fields for image import(eventImage and eventImageAltText), registration (registration) status open(registrationOpens) / close(registrationCloses), private(privateEvent),and publishDate into the event page content type would be very useful and give some very excellent integration for Communico in Views.

Thanks again for your help.

I was able to modify the connectorService.php file to add the 'privateEvents' parameter to this array and could was able to remove Private Events. I'm not sure if there's a way to make this an optional feature for other users. I'll have to make note when any future updates occur with this module so I can patch.

$params = [
'status' => 'published',
'privateEvents' => 'false',
'start' => '0',
'startDate' => $start_date,
'endDate' => $end_date,
'types' => $type,
'limit' => $limit
];

Image style (medium) missing for public://event_images/9971421.jpg. Add the missing style under /admin/config/media/image-styles.

Was getting this error in the dblog. Adding a 'medium' image style to my site allowed the images to display. Thank you very much!

Is there any way to customize which image style is chosen I could see some great value in defining a unique or responsive image style?

jgoodwill01 → created an issue.

jgoodwill01 → created an issue.

jgoodwill01 → created an issue.

Upon uninstall and attempting to reinstall Communico Plus. I'm receiving the following message.

Error message
Unable to install Communico Plus, field.storage.node.field_short_description, field.storage.node.field_subtitle already exist in active configuration.

I'm unable to install after the last update. We do have fields of those names used by other content types.

Thanks,
Jason

earlyburg → credited jgoodwill01 → .

Thanks! It's very encouraging to hear you are still in development on this module. We are currently running Drupal 9.5.9 and the block was being displayed through a paragraph.

Thanks for taking the time to respond. We are constantly trying to find solutions to improve our site, getting communico data into the system would be amazing. I've got some experience with Drupal over the years but am trying to not develop anything in house that would be too difficult for future staff to maintain. If your module was able to simplify the import process and improve visibility for our communico events without over complicating the process that would be great.

ArgumentCountError: Too few arguments to function Drupal\communico_plus\Controller\CommunicoPlusController::__construct(), 0 passed in /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php on line 88 and exactly 2 expected in Drupal\communico_plus\Controller\CommunicoPlusController->__construct() (line 31 of /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Controller/CommunicoPlusController.php)
#0 /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php(88): Drupal\communico_plus\Controller\CommunicoPlusController->__construct()
#1 /websites/lexpublib.org/www/html/lexpublib/web/modules/contrib/communico_plus/src/Plugin/Block/CommunicoPlusBlock.php(29): Drupal\communico_plus\Plugin\Block\CommunicoPlusBlock->buildCommunicoPlusBlock()
#2 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/block/src/BlockViewBuilder.php(171): Drupal\communico_plus\Plugin\Block\CommunicoPlusBlock->build()
#3 [internal function]: Drupal\block\BlockViewBuilder::preRender()
#4 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Security/DoTrustedCallbackTrait.php(101): call_user_func_array()
#5 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(788): Drupal\Core\Render\Renderer->doTrustedCallback()
#6 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(374): Drupal\Core\Render\Renderer->doCallback()
#7 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(204): Drupal\Core\Render\Renderer->doRender()
#8 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(160): Drupal\Core\Render\Renderer->render()
#9 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(580): Drupal\Core\Render\Renderer->Drupal\Core\Render\{closure}()
#10 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(161): Drupal\Core\Render\Renderer->executeInRenderContext()
#11 /websites/lexpublib.org/www/html/lexpublib/web/core/lib/Drupal/Core/Render/Renderer.php(175): Drupal\Core\Render\Renderer->renderPlain()
#12 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(693): Drupal\Core\Render\Renderer->renderPlaceholder()
#13 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(547): Drupal\big_pipe\Render\BigPipe->renderPlaceholder()
#14 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipe.php(305): Drupal\big_pipe\Render\BigPipe->sendPlaceholders()
#15 /websites/lexpublib.org/www/html/lexpublib/web/core/modules/big_pipe/src/Render/BigPipeResponse.php(112): Drupal\big_pipe\Render\BigPipe->sendContent()
#16 /websites/lexpublib.org/www/html/lexpublib/vendor/symfony/http-foundation/Response.php(381): Drupal\big_pipe\Render\BigPipeResponse->sendContent()
#17 /websites/lexpublib.org/www/html/lexpublib/web/index.php(20): Symfony\Component\HttpFoundation\Response->send()
#18 {main}

Thank you. I'm seeing some data now the Communico Plus with Filters block seems to be doing well.

Getting an error with the Communico Plus Block

ArgumentCountError: Too few arguments to function Drupal\communico_plus\Controller\CommunicoPlusController::__construct(), 0 passed in

After looking at the functionality of this module though I don't know if it's going to accomplish what I had hoped. We were looking for a solution to import communico events into drupal to index search and use them as content. Feeds is still lacking Auth 2.0 support to connect to the Communico API and the RSS provided by communico is lacking a lot of event details. I believe this module just pulls data but doesn't provide any way to make it usable in Drupal. Thanks for your help and all your work on this module. Wish it could fill our needs.

Any updates on this patch? Would love to have oath 2.0 feed imports!

jgoodwill01 → created an issue.