wipeoutmedia

Hi there,

Thank you for sharing your concern.
I do apologise for posting about the new update of the CJT plugin in an unrelated Facebook group.

I only just launched this update after almost 6 months, and in my excitement and haste to share the free version of the CJT plugin with others, I posted to a number of WordPress groups, but I believe I may have inadvertently posted in a few unrelated groups such as hosting.

Anyway, I did go through all the posts (which most were already accepted by Admins), but I could not find any of the unrelated ones. Maybe they were already removed. If you can point me to it, I will gladly remove the post.

I hope you have it in your heart to accept the mistake and delete the review.

Hi there,

I am just letting you know that CJT version 11.5 has now ben released with the following changes:

* Compatibility: PHP version 8+
* Compatibility: MySQL version 8+
* Fix: Duplicate ID issue, which on rare occasions was fetching the ‘revision block’ ID for a newly created block causing an error for duplicate entry
* Enhancement: If the ‘wp-content’ directory is renamed to something different (e.g. ‘content’), CJT will now find any custom content directories and install correctly.

Hi there,

I am just letting you know that CJT version 11.5 has now ben released with the following changes:

* Compatibility: PHP version 8+
* Compatibility: MySQL version 8+
* Fix: Duplicate ID issue, which on rare occasions was fetching the ‘revision block’ ID for a newly created block causing an error for duplicate entry
* Enhancement: If the ‘wp-content’ directory is renamed to something different (e.g. ‘content’), CJT will now find any custom content directories and install correctly.

Hi there,

I am just letting you know that CJT version 11.5 has now ben released with the following changes:

* Compatibility: PHP version 8+
* Compatibility: MySQL version 8+
* Fix: Duplicate ID issue, which on rare occasions was fetching the ‘revision block’ ID for a newly created block causing an error for duplicate entry
* Enhancement: If the ‘wp-content’ directory is renamed to something different (e.g. ‘content’), CJT will now find any custom content directories and install correctly.

Hello there,

We have now fixed a number of compatibility issues for PHP version 8+
These fixes will be coming in the next CJT update (version 11.5).

We have tested the plugin with PHP version 8 and version 8.1 and found a couple of breaking changes, which has been fixed as well. We locally set up the environment with PHP version 8 and MySQL version 8 and tested the CJT plugin there. All is working well so far.

Thanks

Hi there,

We have resolved this one, which will be coming in the next update (version 11.5).

This may have been an edge case with the latest version of MySQL (v8).

Even then, the code logic to get the latest ID for the new block needed a rewrite, which was the main reason that new blocks were getting assigned an old, existing block ID.

So we have reworked that function and that fixed the issue. It was initially fetching the “revision block” ID for the newly created block and that’s why there was an error for duplicate entry.

Initial testing is positive, and everything is working well.

Thanks

Hi there,

If you had a custom directory, for example if you renamed your /wp-content directory to something different like /content, version 11.5 (soon to be launched) will now find any custom content directories and install correctly.

Previously the CJT plugin was using some older CONST values to generate a directory path such as PLUGINDIR in combination with ABSDIR. The constant PLUGINDIR is hardcoded in WP core to ‘wp-content’ which is why it will always look for that directory in its core.

However, there’s a different constant value in WP ie. WP_CONTENT_DIR which will always point to the content directory for the WP no matter the name of the directory. When you change the directory name from wp-content to something else, you have to mention that change and a new directory name in wp-config.php. WP_CONTENT_DIR automatically reads those new constants and updates the content dir name on the fly.

I am not 100% sure if this was your issue, but thought we would let you know of this development that fixes a related installation issue.

Thanks

Hello,

Thanks very much for taking the time to write your review and provide some feedback.

I am sincerely sorry to hear that you are not happy we removed features in the free edition. Unfortunately, and as you may appreciate, it takes considerable resources for us to continue to support such a complex project like CJT. It was a super-difficult decision that we did not take lightly. We took a hit, but things are looking more positive with some major improvements coming up in the pipeline.

We hope you continue to support us.

To let you know, we are currently working on a huge update to CJT right here and right now.

Thank you.

Hi there,

Thanks for letting us know that there is an issue with BuddyPress registration pages. We will need to test this further and provide a fix in a future release.

Hello,

Thank you for the follow-up. Now it is my turn to apologise for the delay in replying.

How did you go with ‘saving’ the code blocks?

Also, if you can send us an email directly from our CJT website, we will be able to respond quicker.

Thank you

Hello there,

Thank you for taking the time to post your issue.

This is a strange rare issue that one of the first I have heard of, but I’m here to assist.

Can you please let me know what error message you received? Have you got a filesize limit set for uploading plugins?

By any chance did you manage to resolve it?

Thanks

Hello there,

Can you please try the Chrome browser and again make sure that it is 100% cleared of any cache.

Do you have phpMyAdmin? CJT will never just delete your code blocks as they are stored in the database.

It will only delete your code blocks if you checked the ‘Wipe out Data’ in Settings (cog icon), then Deactivated and Deleted the Plugin. But if you did not do that, then your codes should be safe.

Also try these general troubleshooting ideas below:

– make sure you are running PHP version 7.1 or higher
– increase your PHP Memory limit to 128MB or even 256MB: https://www.wpbeginner.com/wp-tutorials/fix-wordpress-memory-exhausted-error-increase-php-memory
– make sure you don’t have any security plugins getting in the way – e.g. preventing AJAX from working in the Admin dashboard.
– deactivating plugins one by one
– deactivate your theme

Lastly and this is a long shot, according to this support post here, it could be one of two things:

1) The file ‘jquery.block.js’ could be missing in the plugin during the plugin update. Added/modified necessary files in the plugin folder. You may need to download the plugin manually and add that file in.

2) There may be a JS file that seems to be looking for a CSS selector which is apparently missing. The selector class is ‘postbox-header’. Removing that CSS class reference from the JS file may fix the issue. This could be something to do with an older version of WordPress or some other plugin that might be removing that class from the admin area.

If you can post any errors from the CJT dashboard page via the console, that may help.

Thanks

Hello there,

Sorry for the delay in getting back to you.
This is an interesting issue, which we have never seen before. Code blocks must have unique names and if it detects that the same code block name exists, then a new code block cannot be created. So it is strange that another code block was created or duplicated. Are you still seeing this?
Also, when deleting code blocks, you need to press the Save or Save All button so it takes effect otherwise refreshing the CJT dashboard page without doing so, the code blocks will show again. That said, it sounds like when deleting the code blocks, it does not actually disappear at all, which is strange. Thank you for posting the error. This may help us dig deeper.

Thanks

Hello there,

We are very close to releasing the next version. We have considered existing CJT users and believe it makes sense to allow them to continue to have the Aux and Adv tabs. But brand new CJT Free installs, these tabs will be inactive.

I want to thank you for your recommendations on this. Are you able to reach out to us please to discuss and perform a test on this latest version?

Thank you

Hello there,

This looks like a PHP 8 error. Can you let us know if this is still an issue? Did you manage to resolve it?

Thanks