George Pattichis

Hi @arvindwp ,

I am glad you like it and find this useful!

If there are any suggestions for improvements, or any questions, feel free to let me know in the support forum; I’d be happy to help.

Thanks a lot!

Regards,
George P.

Hello @jxb1311 ,

Your suggestion makes perfect sense and I’ve added it to my Todo list. It will be addressed in an update soon.

Thank you for your message!

Best Regards,
George

Hello @arvindwp ,

The option Whether there should be post type archives in my plugin is the equivalent of the has_archive parameter explained here.

What that means, if you select YES in the above option, is that your newly created CPT, let’s say “Books“, will have an archive displayed at https://yourdomain.com/books/

Responsible for the layout of that archive page would be one of the templates as explained in the template hierarchy of WordPress. In our “Books” example, WordPress will look for archive-books.php, if it is not found it will use the generic archive.php and if that is missing it will render the page using index.php. You can use a child theme to customize those templates.

However, you can of course override WP’s default templating mechanism by creating your own queries. The WP_Query is a powerful tool that allows to query and display any kind of data we want from our WP database. The post_type parameter gives us the option to query for any CPTs we want. There’s code example in the previous link on how to display multiple post types, including custom post types.

There are also a dozen of other ways to query posts, and display them to a page, depending on your theme, page builders, addons or editor blocks you might be using.

Hope this helps at least a bit and I am glad you figure it out!

Regards,
George

This was actually a false positive and the Wordfence team has resolved it on their side already.

There was never a vulnerability with this plugin and the notice will be cleared in the next scan.

Hi again,

I just got a confirmation from the Wordfence team that it was a false positive and there was never really a problem with my plugin.

They have alredy resolved it on their side and the notice will be cleqred in the next scan.

Thanks again for informing me.

Hello jerryrcole,

Thank you for informing about this. I have contacted the Wordfence guys to get more details on how to resolve this issue. I will be uploading an updated version asap, to satisfy their security scanner.

Best regards,
George

• This reply was modified 2 years, 1 month ago by George Pattichis.

Hello @masudwork,

Thank you for your kind words.

I believe you are missing the point of this plugin so please let me briefly explain. This plugin does nothing more that what is already available in WordPress by default.

Registering a Custom Post Type (CPT) in WP is done by writing code, as explained here, and specifically using the register_post_type function.

As a developer, I found myself constantly writing similar code to register CPTs for my clients’ websites and in order to speed-up this process I decided to create a Graphical User Interface to do exactly that. And since there are many WP users that are not very keen with code, or don’t have access to edit their files, I’ve packaged that into a free plugin and released it here. Same goes for custom taxonomies.

As soon as you use this plugin to create a CPT, then it is up to your theme to use those posts in the frontend of your website. Just like the default post types: Posts or Pages.

For example, if you create a CPT named books (with my plugin or custom code, it doesn’t matter) then you will find a new menu in your admin dashboard called Books. Just Like Posts. You then add your Books there and you can see them in the frontend by clicking on their permalinks or visiting their archives. Again, just like Posts/Pages. A tip here, you can use ACF (or similar) along with my plugin to further extend the functionality of your CPTs.

If you want your CPT to have a different frontend view, in single or archive pages, then this is a very abstract task that goes well beyond this plugin’s scope. I wouldn’t know how your theme looks in the frontend, so how can I add a custom styling to display your CPT? Your theme is responsible for that.

Having said the above, if you tell me what exactly you are trying to achieve, I might be able to point you to the right direction. What you want to do is probably already available in WordPress core or in your theme.

Hope this clears things up,
George

Hi @scottistrand ,

You can now update the plugin as usual and those warnings will be gone. I have also tested the plugin with WordPress latest version and all is well.

Please do let me know if you have any other issues or if you have any suggestions for improving this plugin.

I would also appreciate it if you could spend a second to give your honest review.

Thanks again!

Hello @scottistrand ,

Those are actually warnings, not errors, so they won’t really break anything.

However, since I don’t like my error logs being filled with unnecessary warnings either, I will be uploading an update to the plugin very soon to handle both issues.

Thank you very much for reporting this!

Having the same error on a client’s website where Booster Plus is installed with a valid license.

Booster is updated to the latest version, v5.4.8, but the error still exists.

Wetransfer uploads are only valid for 7 days. Can you please provide the solution for everybody else please? Thanks!

Simplest way to do this is to go to Spotify, find the playlist you want, click the three dots, click Share -> Embed and copy the code. For example, you will get something like this:

<iframe src="https://open.spotify.com/embed/playlist/5FTG4h3A1kpX0eQSfURjn8?theme=0" width="100%" height="380" frameBorder="0" allowtransparency="true" allow="encrypted-media"></iframe>

Then go to your WordPress post/page editor, insert an HTML block and paste the above code.

Preview or Save/Update and View your Post/Page. It should now show the embedded playlist since this is simple iframe based.

If it does not, please open up your browser’s console and check for errors. If you see any errors please paste them here.

• This reply was modified 3 years, 3 months ago by George Pattichis.
• This reply was modified 3 years, 3 months ago by George Pattichis.
• This reply was modified 3 years, 3 months ago by Steven Stern (sterndata).

Hello @alframe ,

This is actually a warning, and I can resolve it but I am having trouble replicating the issue here and I would like to know how it was created in the first place.

Can you please go to the options page and make a change in the Post Type section (the checkboxes), save your option and let me know if the warning still exists?

The options page is here:
/wp-admin/options-general.php?page=clone-posts-options

By the way, I’ve already uploaded a new version that will handle this issue if it appears, so by updating the plugin the warning will go away.

Thank you for reporting this!

• This reply was modified 3 years, 3 months ago by George Pattichis.

Hi Zverinetz,

I am glad you like it!

If you have any ideas to improve it or any feature requests feel free to post in the support forum, thank you!

George

Hi @ollidoetsch,

I am glad you like it!

If you have any ideas to improve it or any feature requests feel free to post in the support forum, thank you!

George

You are right, that trailing comma causes a fatal error in earlier versions of PHP. I have just uploaded an update with the fix for backwards compatibility.

@johndonovan , @deltafactory thank you for reporting this.