cyclonecode

Hello. This could be caused by a limitation from your hosting provider. I can have a look at this if you could send me the output from the plugins status page. Do not post the output here, instead either join my slack channel and send me a message there: https://join.slack.com/t/cyclonecode/shared_invite/zt-6bdtbdab-n9QaMLM~exHP19zFDPN~AQ or send me an email at [email protected].

Too bad you think so, but again no one is forcing you to use it. Could you point out what parts you think is badly coded and I can try to refactor those parts.

One of the reasons for pushing towards premium is obviously to actually get something back from this. Not sure you understand how much time and effort it takes to handle an open source project with 10k+ users?

You can not use Custom PHP Settings to upgrade your current PHP version, since this involves actually installing new binaries on your filesystem. You will need to ask your hosting about how to move forward with this.

This issue should be resolved in the latest version 2.1.0. I still think I actually will drop support for PHP 5.6 and only support 7.0+ which would make things much easier to maintain.

The updated code looks like this:

$parameterClass = @$parameter->getType();

I actually already do this. I think I could refactor the code in the php-di package and use https://www.php.net/manual/en/reflectionparameter.gettype.php instead which would solve this problem for PHP 8+.

The warning comes from the PHP-DI package and is kind of hard to resolve without switching to some other DI container since I would like to support PHP 5.6+ which means I cannot bump the PHP-DI package to any later version. I would really like to drop support for PHP 5.6, but thinking that there might be many users that still sits on this very outdated version.

I will think some more =)

No problem, glad I manage to solve it pretty fast. I am closing this as resolved now.

Now I have created a patch that solves this issue. Download and install the latest version 3.0.1 and the problem should be fixed.

Changing the namespace from CisionBlock\Trait to CisionBlock\Traits fixes this issue. This only seems to be a problem in PHP 7.4.
The reason is that trait being a reserved keyword in PHP.

Hello

I have not seen this before or had any problems related to it, but after some investigation it seems like this could be caused by me using “Trait” in the namespace. I will try to refactor the code and see if that solves it. Since I am not able to reproduce the error it would be awesome if you could send me your email address at [email protected] or join my slack channel so we can test if the fix work for you setup or not.

This is only a warning, but I will have a look on it.

When using the search_term we filter the news feed based on items where either the title or content contains the search_term string.
The premium version has much better support for searching based on title, content and tags since it supports creating posts within WordPress.

Then you would need to override the template used to render a single article by copying the following file cision-block/src/Frontend/cision-block-post.php into the root or into a templates folder in your active theme, then you can add something like this in the template in order to display a date for the post:

<time><?php echo date('Y-m-d H:i:s', $CisionItem->PublishDate); ?></time>

Hope this helps.

• This reply was modified 1 year, 6 months ago by cyclonecode.

Yes, you should be able to do this by changing the date format under the settings page, for instance using H-i-s would display the hour, minute and second the post was published. You can read more about the different time formats here: https://www.php.net/manual/en/datetime.format.php

This issue is resolved in version: 1.4.4.