JetEngine v2.4.0 Beta

[MjHead]

Hi,

We are almost getting ready to release JetEngine v2.4 and we would like to ask you to help us test JetEngine v2.4.0 Beta.

You can download beta version from your Crocoblock account.

New Data Stores module

The new module allows the administrator to create different data stores, to which users will add their posts. The point is that each user will have their own personal repository, i.e. there will be only those posts added by the user. This functionality allows you to implement such things as wishlists, compare, favorites, likes to posts, and any other collections of posts that users can create. In the future, a simplified basket will be added.

When the module is activated, a new menu item, Data Stores (http://prntscr.com/s8ld80), is added to the JetEngine Dashboard. Here are the Settings:

• Name — the name of the store that will be displayed in the settings related to the widget stores;
• Slug — the slug of the store or its system name; the data will be stored in the selected storage under this very name;
• Store type — a type of the store. This is the place where the data will be physically stored. There are currently 4 available store types — Browser cookies, Session on the server, Local browser store, User metadata (available only for logged-in users);
• Max size — the maximum number of posts in the store;
• Count posts — to count or not to count the number of times the current post has been added to the store.

You can add/remove posts from the store using the Dynamic Link widget. Two new sources were added to this widget — http://prntscr.com/s8lisu. To set it up, you’ll need to select the store. When adding posts to the store, you can also set the text and widget icon that will be displayed if the post is already there.

You can display posts from the current store using the Listing Grid widget. For this reason, there is a new Get posts from store option that can be found in the Posts & Author Parameters section within the Posts Query section settings — http://prntscr.com/s8lro1. Here you can choose to display the posts from a particular store. Everything else works as it would normally do with the Listing Grid widget.

In addition, 2 dynamic tags were added — http://prntscr.com/s8lsvf.

• Post Count — displays how many times the current post has been added to different users’ stores.
• Store Count — displays the number of posts in the store for the current user.

Dynamic Visibility module for Sections/Columns/Widgets

Now, it is possible to show or hide the Elementor components (sections, columns, widgets) depending on the dynamic values of the current page/post.

It is implemented as a separate module, so first, you need to enable it in the plugin settings: https://prnt.sc/s81wr4. Then, you’ll see the Dynamic Visibility section in the Advanced tab for all Elementor components, including its settings — https://prnt.sc/s81zla.

Ability to create repeater groups in the Forms

Within the Forms module, it became possible to combine several fields into a repeater group. It works similarly to a Repeater in meta fields and has the same purpose. The main difference is that it is a separate type of field when it comes to meta fields, and in the Forms, these are 2 ‘wrapper’ fields — the beginning of the repeater and the end of the repeater. All fields that go inside these ‘wrapper’ fields automatically compose a repeater group. Calculated fields, which are inside the repeater group, calculate the result inside the current group. Calculated fields, which are outside the repeater group yet having a Repeater field in the formula, calculate the result as of the entire Form, while the repeater fields are summed up taking into account the options (for more details, see the next block).

In the Form’s Field Settings, there are 2 new field types — Repeatable Fields Group Start and Repeatable Fields Group End (http://prntscr.com/s8jd5b). All fields that go between these two fields will compose a repeater group — http://prntscr.com/s8jf0d, http://prntscr.com/s8jkqh. The Repeater-related settings are gathered in the Start field — http://prntscr.com/s8jljt.

• Manage repeater items count: allows you to manage the number of repeater items manually or set it from a field in the Form (for example, the number of guests and fields for each guest);
• Add New Item Label: a label for the Add New Item button;
• Calculate repeater row value: calculate the value of the entire group (if the field is used in some formula — Repeatable Fields Group Start) using the formula or simply bring back the number of repeater items;
• Calculation Formula: formula for calculating if you selected Custom (calculate custom value for each row) in the previous field. In the Form widget settings in Elementor, there has been added a section with the style settings for the repeater elements.

Conditional logic for the meta fields

We’ve added the ability to hide/show meta fields depending on the value of other meta fields. This is very convenient for showing/hiding of the related fields. Example: https://prnt.sc/q36d5k.

There is now the Conditional Logic option in the meta field settings. Once activated, it pulls the Repeater, through which you can set the meta field display rules. In the Rules settings, one can select the name of the conditional field, operator, and the value upon reaching of which the current field should be displayed. For conditional field types such as Select, Radio, Checkbox, Switcher, the possible values are pulled automatically to the Value field: https://prnt.sc/s81bu8.

If you delete a meta field from the list of fields, provided that it was in the Condition rules, it should be removed from them, too.

Conditional logic for the fields in the Forms module

It is now possible to add conditions for showing/hiding the Form fields depending on the other fields’ values.

In the Fields Settings editor, there is a new button next to all fields of the Form that stands for configuring the Conditional logic — http://prntscr.com/s8kvml. When you click on it, it’ll open the Conditional logic editor, in which you can set an unlimited number of conditions for one field — http://prntscr.com/s8kxmd. Here are the settings:

• Type — rule type — allows you to show the field if the condition is met, hide the field if the condition is met, set the field value if the condition is met, set the calculated field value if the condition is met;
• Field — this field’s value is going to be checked;
• Operator — the condition, by which the field will be checked — more, less, equal, one from the list, in the range from-to;
• Value to compare — this value will be compared with the value of the selected field. For the Between condition, you need to specify 2 values ​​separated by commas; for the In the list condition, specify the number of values ​​in the list, separated by commas;
• Value to set — the value that must be set for the current field if the condition is met.

Ability to delete posts from the front end

This feature can be used in conjunction with the front-end posts submission to enable users to delete posts that they added.

For the Dynamic Link widget, we’ve added a new source — Delete current post link, http://prntscr.com/s8l5jp. Additional settings are below:

• Confirm deletion message — when you click on it, a system popup will appear asking to confirm the deletion. This option allows setting the text of this popup;
• Redirect after delete — where a user will be redirected after post deletion;
• Delete post type — move a post type to trash or delete once and for all.

Ability to set the Input mask for the text fields in the Forms module

It is now possible to set input masks for the desired text fields in the Forms. This feature can be used to input phone numbers, specific numerical data such as card numbers, dates, etc.

For the text fields in Forms, we’ve added a new block with the Mask settings — http://prntscr.com/s8m8el, where:

• Mask type — default digital value or date;
• Input mask — the mask itself;
• Mask visibility — allows choosing the visibility mode: always, only when hovering on the field, only when focusing on the field;
• Mask placeholder — a symbol that will be used as a placeholder for an empty mask; for example, if you select *, the mask will look like this: - - - .

Ability to set the maximum number of user-generated posts depending on a user (a Profile Builder setting)

We were often asked to limit the maximum possible number of posts a user can add on the site. This feature allows you to set such a restriction. It is added as a Profile Builder setting, as the addition/editing of posts is implemented in the context of the Profile Builder functionality. In the future, these settings will most likely change a lot.

In the Profile Builder settings of the profile of the builder, there’s now the Advanced section — http://prntscr.com/s8mdcu. In this section, a user can set restrictions for the selected roles and set custom error text that will pop up whenever a certain user tries to add a new post. If the same role is used several times in different rules, then the last rule containing this role will work.

Support of the Select, Radio, and Checkbox fields in the Repeater meta field

From now on, it is possible to extend the Repeater meta field with such field types as Select, Radio, and Checkbox — https://prnt.sc/s7gk31.

Support of the Number field type for the meta fields

From now on, it is possible to store numerical metadata in the Number field type — https://prnt.sc/s7h2j7. We’ve also added the ability to use it inside the repeater. The additional options are Min value, Max value, Step value.

Random number of posts in the Listing Grid

This feature was requested by the customers: https://github.com/Crocoblock/suggestions/issues/389. The feature works like this: when you reload the page, the number of posts in the listing is changed randomly. It is especially interesting to observe when working with a slider and when the random sorting of posts is set up. With each page reload, we get a different number of different posts.

The widget now contains an option that is meant to switch on this functionality — Use Random posts number. When enabled, the Posts number option will indicate the minimum possible number of posts, whereas the new Max Random Posts number option will indicate the maximum possible number of posts. It has been done for control over the random number of posts in some cases to avoid the instances when the system displays 1 or 999 posts.

Automatic conversion of Cyrillic to the Latin alphabet in the Name meta field

When adding a meta field and filling in the Label field, the Name field is generated automatically based on the Label field. Previously, if the Label field was filled in using the Cyrillic alphabet, the generated Name field contained the same Cyrillic letters, which is not very good. The clients left it without any changes. Now, when the Name field is automatically generated, the Cyrillic letters will be converted to the Latin alphabet. This also applies to instances of manual changing of the Name field — https://prnt.sc/ozms27.

Prevent duplication of the meta field names

Sometimes, during the addition of the meta fields, the clients assigned to several of them with the same names. As a result, duplicated meta fields did not appear where necessary. Now, if you accidentally name several meta fields similarly, such a field name will be given a prefix with a random number, as an indication of the name duplication: https://prnt.sc/s7vs30.

Support of SVG images preview in the Media meta field

This feature was added at the customer’s request: https://github.com/Crocoblock/suggestions/issues/1102.

Now, when adding a Media field and selecting an SVG image in it, the preview should not be empty. As to specific formats (video, audio, PDF), the preview should display an icon for the corresponding format, and the file name should be immediately visible.

Notes

For bugs and remarks, please reply with a comment on this issue here on GitHub.

Please keep this related to the Current beta Only! any other issue or feature request, feel free to open a new issue.

Many thanks for your support and help!

[Deswegen]

I noticed the new "Dynamic Visibilty" section/function could use an indication if it is enabled (a bit faded or some text indication). For now you can't really see if it is active if you are not having the options open)

But really AWESOME!!!! Already playing around and looking really good. A lot of things we needed.

[MjHead]

I noticed the new "Dynamic Visibilty" section/function could use an indication if it is enabled (a bit faded or some text indication). For now you can't really see if it is active if you are not having the options open)

But really AWESOME!!!! Already playing around and looking really good. A lot of things we needed.

Thanks for feedback, we'll try to implement this until stable version release!

[Deswegen]

Just tried to do the following and noticed it's not working, think might be a bug: I have a custom post type "Events" where I added a "Switcher" Field "Do you want to add a schedule" which is followed by a repeater field where I set the conditional logic to just visible if the Switcher field is set to equal "on". But as soon as I set the c.d. it does not show at the cpt page. If I turn the conditional off, it shows again.

So I think if you try to show a repeater field based on a conditional logic "Switch", it might be bugged at the moment. With other field types, the conditional logic works fine (although not tested all of them yet).

[MjHead]

@Deswegen Thanks! We'll check this!

[Lonsdale201]

Just tried to do the following and noticed it's not working, think might be a bug: I have a custom post type "Events" where I added a "Switcher" Field "Do you want to add a schedule" which is followed by a repeater field where I set the conditional logic to just visible if the Switcher field is set to equal "on". But as soon as I set the c.d. it does not show at the cpt page. If I turn the conditional off, it shows again.

So I think if you try to show a repeater field based on a conditional logic "Switch", it might be bugged at the moment. With other field types, the conditional logic works fine (although not tested all of them yet).

The switcher value is " true, or false" depend on or off state, or i thinking wrong?

[MjHead]

@Deswegen Its mislead with Switcher field - visually it shows On/Off labels, but in the database its stored as @Lonsdale201 correctly mentioned, as true/false, so you need to set 'true' into Value field of Dynamic Visibility - http://prntscr.com/soqkas, we'll add special operators to check JetEngine switchers to avoid such mislead

[Lonsdale201]

@Deswegen Its mislead with Switcher field - visually it shows On/Off labels, but in the database its stored as @Lonsdale201 correctly mentioned, as true/false, so you need to set 'true' into Value field of Dynamic Visibility - http://prntscr.com/soqkas, we'll add special operators to check JetEngine switchers to avoid such mislead

Mr Mjhead. Before you are created this new epic dynamic visibility function, i used the Dynamic Conditions plugin, to achive this. But this dynamic visibility we can make more complex system. Formerly, with the Dynamic Conditons(plugin), cant achive to coniditions with your Checkbox meta.(except, if used the jet 2.3 new features to add custom checkbox value.) The database with the jetengine meta checkbox - storing very complicated, maybe that was cause the conflict. I created lot of new functions with this new 2.4 beta. ( compare system, favorit sytem, like system, and more complex backend meta structure.) But i not tested yet. But, with your new dynamic visibility functions, we can control the checkbox value too?

And, in a near future, are you plan to make possible configurate with the Listing widget, set listing option with checkbox values? ( ex: list cpt(s) with specific checked values) -> I tried to make this, but it didn't really work only in one part. Thanks in advance, and again for this big epic update ! :)

[MjHead]

@Lonsdale201 as for checkboxes values in the Dynamic Visibility module - we'll check how to do this in the most convenient way. As for Listing grid and checkboxes - could you please describe your case a bit more detailed, not sure I understand you properly

[Lonsdale201]

@Lonsdale201 as for checkboxes values in the Dynamic Visibility module - we'll check how to do this in the most convenient way. As for Listing grid and checkboxes - could you please describe your case a bit more detailed, not sure I understand you properly

Thanks for your reply.

Well, let's see a simple example to trying explain little bit more.

1, In our case, i created a "game" custom post type. I made many meta box, and make a Checkbox meta field calling "Genre" with game type values. ( fps, mmorpg, etc..)

2, Next, i create some post within the games cpt.

3, I create a simple page Calling "Games" I'd like to show some game cpt(s) inside this page. So i using the JetEngine listing widget. 4, I can create featured cpt, or anything i can image, but i would like to create a specific listing with show only "FPS type of games with pulled dynamic data from genre checkbox". I early created a genre checkbox meta field. I settinged some fps game, and others.

In the listing grid widget : Posts query -> Meta Qery -> I set the Key to my checkbox meta ID (in our case genre) I set the operator Beetween, or Equal or other nvm. On the value list, i added the checkbox value like FPS (my checkbox value and database equal to "FPS". in theory)

Not showing. I tried to playing with the Type set Signed, or Unsigned, but unfortunately to working.

Of course, this can do anything other options example with terms, but i guess usefull option if the listing widget have checkbox rules too.

[Lonsdale201]

Meanwhile i tested the Dynamic Visibility option with Checkbox.

I share my suggest:

Maybe create two more Condition: "Checkbox Include, Checkbox Exclude", or something similar?

The radio option work fine.

Btw in the coniditon list: The In the list, and Not in the list, what controlling exactly? :)

[MjHead]

• As for listing grid - yes, I got your point, I'll think how we can implement such option and hope we'll find solution until 2.4 stable release.

• As for Dynamic Visibility and checkbox - yes, you are right, we already working on it, tomorrow we'll release Beta 2 and you'll can test it.

• As for In the list, and Not in the list conditions - with this condition you can check if your current meta field value is equal to one of the comma-separated values from the specified list. For example if you have meta box Genre of game and want to show some info only if game has genre arcade, fps or strategy. You can get same logic by adding multiple conditions for same mea field with OR relations, but the differnce is In the list condition could also process meta fields stored as arrays. So, by the way, it can be used to handle checkboxes - you set Checkbox meta field into Field option and value which you want to be checked into Value option, its not most obvious way, but it will work :)

[Lonsdale201]

All clear, and thank how you are always open for the suggestions.

One more remark with the beta. Very very rarely, when i using the dynamic logic system on the backend inside the cpt, sometime, broken the update option in the post. (not the form).

Otherwise good to see, you started the create the membership functions piece by piece. With the new rule module Under the profile builder open lot of new way to boost the front end submission. Please if have time, dont forget to update the language template. Im translating your Plugins to my language (hungary), in the JetEngine i done 40%.(JetPopup 90%) But have lot of missing parts :(

Sincerely Soczó Kristóf.

[MjHead]

All clear, and thank how you are always open for the suggestions.

One more remark with the beta. Very very rarely, when i using the dynamic logic system on the backend inside the cpt, sometime, broken the update option in the post. (not the form).

Otherwise good to see, you started the create the membership functions piece by piece. With the new rule module Under the profile builder open lot of new way to boost the front end submission. Please if have time, dont forget to update the language template. Im translating your Plugins to my language (hungary), in the JetEngine i done 40%.(JetPopup 90%) But have lot of missing parts :(

Sincerely Soczó Kristóf.

Thanks for feedback and kind words :) We'll try to catch a bug with dynamic logic and update translation with Beta 2

[realstephenzhao]

It's really a major update, I'll look through these new functionalities later.

[Lonsdale201]

All clear, and thank how you are always open for the suggestions. One more remark with the beta. Very very rarely, when i using the dynamic logic system on the backend inside the cpt, sometime, broken the update option in the post. (not the form). Otherwise good to see, you started the create the membership functions piece by piece. With the new rule module Under the profile builder open lot of new way to boost the front end submission. Please if have time, dont forget to update the language template. Im translating your Plugins to my language (hungary), in the JetEngine i done 40%.(JetPopup 90%) But have lot of missing parts :( Sincerely Soczó Kristóf.

Thanks for feedback and kind words :) We'll try to catch a bug with dynamic logic and update translation with Beta 2

Thank you. One more remark, what i found.

I created a compare system with new Data storage function. This work well, but i tried to combo with JetPopup. ( create custom notification popup after applied the compare) Using a same method, as though a quick view function. Unfortunately if i set the popup with the Dynamic Link widget, in the listing editor, the popup show, but the data storage function does not apply. Maybe bug, or these not fit side by side?

[antonio86itna]

I like your plugins because it is easy to customize them with elementor so it is the best to save time.

I can guarantee you that there are 2 things you need to add and it should be your priority to reach and surpass the acf + cpt pair:

1) You must add the possibility to change the slug of the post type, but only the slug of the single post and not everything (archive, single post etc.) In cpt there is the rewrite option to change only on the single post.

To give you an example if I create a post type and call it "vehicles" then the single post of a bmw for example "bmw x6 TDI" the slug in your case will always be / vehicles / while normally in the single post it should be singular therefore / vehicle / this on jet engine still cannot be done I saw in the beta, while in cpt it is a professional thing that I recommend you insert as soon as possible.

2) Very urgent need to insert a feature that I already asked you months ago. I guarantee you that it is one of the most important things to insert and that it makes many users choose cpt rather than you. If you implement this, you will be unrivaled, because jet engine is much easier than cpt + acf. The function you have to insert is: The possibility to create the meta fields separately and choose for which post type they must be inserted or for which specific taxonomy, then the custom fields will be loaded after selecting the taxonomy. So they don't have to be specific to the post type in general. Now I'm recording a video to show it to you.

[MjHead]

@antonio86itna Thanks, we'll looking into it :)

[MjHead]

@Lonsdale201 Thanks, we already checking this. For now - we released Beta 2 version with updated translations, added visual indication for elements with Dynamic Visibility enabled and a bit refined Dynamic Visibility options

[Lonsdale201]

@Lonsdale201 Thanks, we already checking this. For now - we released Beta 2 version with updated translations, added visual indication for elements with Dynamic Visibility enabled and a bit refined Dynamic Visibility options

Awesome. Thankyou especially for the transition update. As you make it avaliable for the Beta2 i will jump into to testing ^^

Btw. I continued the testing. I thinking about, maybe can i create public like system with the new data storage option. (I stretch the boundaries)

But i guess im wrong. I tried to use the storage type : Session. (because this like system enable for visitors and storage to my server) Well i added the add store and remove dynamic link widget on the Listing item and a counter too, and also tried to add this for the global cpt temaplate too.

The results:

If i hit the Like one of listing item on some page where i used the Listing grid widget. Every post counter increase one time. This storage option should it work separately, or im wrong?

After, if i hit the remove button, the selected post disappear for my Listing grid items.

So show 3 post. If i hit the like all post counter show 1, not only where i applied. If i try to remove(hit dislike), the selected post disappear for the listing widget, on the frontend.

So Idk, its a bug, or i thinking total wrong for the Session storage type function?

Other peoples trying my like function, and he have other counter results. But this session storage data to my server, why show different results for the visitors? Or the session, not equal for this option?

Image attached, maybe helping.

[dennylai1990]

An option to change background colour when added to store should be included for better differentiation between listings. https://prnt.sc/sphqs3

[Lonsdale201]

Huh, another remark?

Just testing, the condiiton logic for the metabox in the backend. In the Conditon options, i guess useful option if can select Empty or, Contains or other similar condition option. This helping a lot for the text fields to make chain conditions. (just idea)

And, the Tab options. (Objective type - Tab). In a future, will be controlling with the conditions too? Helping a lot make more transparent for the metas sorting.

[Lonsdale201]

Number field - Dynamic logic condition bug (backend -cpt post)

Finally, i found what break the post update ( on backend ). The new number field. I Settinged two Number field. Fix price, and monthly price. I Settinged the condition logic, if the Fix price meta empty, showing the Monthly price Number meta. If the fix price meta get value , the monthly price will be disable(this i want so its good), but, still i using the conditional logic with the number meta fields, i cant update the post. So if i want to update my cpt post need to disable the attached conditional logic on the number meta(s).

[dennylai1990]

I'm testing out the Data Stores Module, and here's what i think would make it better. 1) The ability to determine Maximum posts allowed to store via user roles. Use case: Membership site. Higher the membership tier/user role (including non-logged in users), unlocks ability to "save" more posts. 2) The ability to be able to style (hopefully in elementor) & customize error message when "Maximum posts allowed to store" exceeds set limit. Even better if error message can be customized and changed according to membership tier/user role "Maximum posts allowed to store" limit. See https://prnt.sc/splzpo 3) (Duplicate from previous post) An option to change background colour when added to store (both normal and hover states) should be included for better differentiation between saved and unsaved listings. https://prnt.sc/sphqs3 4) The ability to "sync" listings using ajax for the data stores module. Use case: https://bit.ly/3guVOVD 1) "Save" a post 2) Go to the "save archive". You'll see your saved post in 3 different positions/layouts. 3) Delete one of your saved post. Notice that it does not sync with the rest of the listing modules unless the page is refreshed.

[dennylai1990]

Found some bugs on JetEngine v2.4.0 Beta2, when used in conjunction with Jetpopup and JetEngine listing. I have a listing and a button(only viewable on mobile) that triggers a popup using Jetpopup(ajax,force loading). I pull the text field "Stock Symbol" using the dynamic field widget and the featured image using the dynamic image widget in the popup, but it seems like its not able to pull the data. On JetEngine v2.3.6, i wasnt able to pull taxonomy using the Dynamic Terms widget but it seems like its working on v2.4.0 Beta 2. Here's the video. https://www.youtube.com/watch?v=sbTUc4nyaTc&feature=youtu.be I hope it's not confusing.

[kaskad88]

Number field - Dynamic logic condition bug (backend -cpt post)

Finally, i found what break the post update ( on backend ). The new number field. I Settinged two Number field. Fix price, and monthly price. I Settinged the condition logic, if the Fix price meta empty, showing the Monthly price Number meta. If the fix price meta get value , the monthly price will be disable(this i want so its good), but, still i using the conditional logic with the number meta fields, i cant update the post. So if i want to update my cpt post need to disable the attached conditional logic on the number meta(s).

@Lonsdale201 Could you please attach a screen or describe more detailed, because I tried to reproduce your issue based on the information you provided, but without success.

[Deswegen]

Maybe also handy to add this functionality: Just wanted to adjust the width of a repeater field for the backend (so that two fields are next to each other) and noticed you do not have that option, as you do with other fields (field width 100%, 75%, 66,66%, ...). Not a must have, but nice in order to clean up the back-end.

*Screenshot of the section i mean: https://freeimage.host/i/Jwz6lI

[MjHead]

@Lonsdale201 Thanks, we already checking this. For now - we released Beta 2 version with updated translations, added visual indication for elements with Dynamic Visibility enabled and a bit refined Dynamic Visibility options

Awesome. Thankyou especially for the transition update. As you make it avaliable for the Beta2 i will jump into to testing ^^

Btw. I continued the testing. I thinking about, maybe can i create public like system with the new data storage option. (I stretch the boundaries)

Hi @Lonsdale201, as for removing post from listing grid - we added option to avoid such cases. As for count posts - its work fine for me. What dynamic tag did you used for this counter - Post Count or Store Count? For such case you need to enable Count posts in the store options and use Post Count dynamic tag. Why - Store Count is dynamic tag which shows count posts in the current store for current user, for your case it will be total number of user likes. Post Count shows how many times this post was added into this store by all users, so for your case it will be total likes count (exactly what you need)

[MjHead]

Maybe also handy to add this functionality: Just wanted to adjust the width of a repeater field for the backend (so that two fields are next to each other) and noticed you do not have that option, as you do with other fields (field width 100%, 75%, 66,66%, ...). Not a must have, but nice in order to clean up the back-end.

*Screenshot of the section i mean: https://freeimage.host/i/Jwz6lI

Thanks for suggestion we'll add this to roadmap for 2.4.x updates

[MjHead]

I'm testing out the Data Stores Module, and here's what i think would make it better.

1. The ability to determine Maximum posts allowed to store via user roles. Use case: Membership site. Higher the membership tier/user role (including non-logged in users), unlocks ability to "save" more posts.
2. The ability to be able to style (hopefully in elementor) & customize error message when "Maximum posts allowed to store" exceeds set limit. Even better if error message can be customized and changed according to membership tier/user role "Maximum posts allowed to store" limit. See https://prnt.sc/splzpo
3. (Duplicate from previous post) An option to change background colour when added to store (both normal and hover states) should be included for better differentiation between saved and unsaved listings. https://prnt.sc/sphqs3

Hi! Thanks for suggestions, background for added to store link we'll add into 2.4 Beta 3, the rest we'll try to implement with 2.4.x updates

[MjHead]

Huh, another remark?

Just testing, the condiiton logic for the metabox in the backend. In the Conditon options, i guess useful option if can select Empty or, Contains or other similar condition option. This helping a lot for the text fields to make chain conditions. (just idea)

And, the Tab options. (Objective type - Tab). In a future, will be controlling with the conditions too? Helping a lot make more transparent for the metas sorting.

Thanks for suggestions, yes we planning to extend conditional logic with these features with next updates :+1:

[MjHead]

I like your plugins because it is easy to customize them with elementor so it is the best to save time.

I can guarantee you that there are 2 things you need to add and it should be your priority to reach and surpass the acf + cpt pair:

1. You must add the possibility to change the slug of the post type, but only the slug of the single post and not everything (archive, single post etc.) In cpt there is the rewrite option to change only on the single post.

To give you an example if I create a post type and call it "vehicles" then the single post of a bmw for example "bmw x6 TDI" the slug in your case will always be / vehicles / while normally in the single post it should be singular therefore / vehicle / this on jet engine still cannot be done I saw in the beta, while in cpt it is a professional thing that I recommend you insert as soon as possible.

1. Very urgent need to insert a feature that I already asked you months ago. I guarantee you that it is one of the most important things to insert and that it makes many users choose cpt rather than you. If you implement this, you will be unrivaled, because jet engine is much easier than cpt + acf. The function you have to insert is: The possibility to create the meta fields separately and choose for which post type they must be inserted or for which specific taxonomy, then the custom fields will be loaded after selecting the taxonomy. So they don't have to be specific to the post type in general. Now I'm recording a video to show it to you.

Hi @antonio86itna! Thanks for suggestions, we'll try to implement this with 2.4.x updates

[Lonsdale201]

@Lonsdale201 Thanks, we already checking this. For now - we released Beta 2 version with updated translations, added visual indication for elements with Dynamic Visibility enabled and a bit refined Dynamic Visibility options

Awesome. Thankyou especially for the transition update. As you make it avaliable for the Beta2 i will jump into to testing ^^ Btw. I continued the testing. I thinking about, maybe can i create public like system with the new data storage option. (I stretch the boundaries)

Hi @Lonsdale201, as for removing post from listing grid - we added option to avoid such cases. As for count posts - its work fine for me. What dynamic tag did you used for this counter - Post Count or Store Count? For such case you need to enable Count posts in the store options and use Post Count dynamic tag. Why - Store Count is dynamic tag which shows count posts in the current store for current user, for your case it will be total number of user likes. Post Count shows how many times this post was added into this store by all users, so for your case it will be total likes count (exactly what you need)

Thanks. ^^ Yes, Idk why i used the Store count, instead post count... But, the removing post from listing grid if i use the remove store button still there . Or i missed to set one more thing?

[MjHead]

@Lonsdale201 We fixed this but not yet uploaded version with this fix to Crocoblock account

[Lonsdale201]

Number field - Dynamic logic condition bug (backend -cpt post) Finally, i found what break the post update ( on backend ). The new number field. I Settinged two Number field. Fix price, and monthly price. I Settinged the condition logic, if the Fix price meta empty, showing the Monthly price Number meta. If the fix price meta get value , the monthly price will be disable(this i want so its good), but, still i using the conditional logic with the number meta fields, i cant update the post. So if i want to update my cpt post need to disable the attached conditional logic on the number meta(s).

@Lonsdale201 Could you please attach a screen or describe more detailed, because I tried to reproduce your issue based on the information you provided, but without success.

Sir, i tried to remake this issue, but now everything is fine. But, if i again running into this, i will capture a video.

Anyway, the issue it was before, On the backend -> Created two number meta. Fix price / monthly price box.

For the monthly price box i settinged the condition logic -> Selected the Fix price field -> Added In the list operator, and not filled the value list. (because, if the fix price empty showing the monthly meta box) And when i testinged, two time running into to break the backend page update. If i switched off the condition logic for the monhtly price number meta field, the problem solved.

[MjHead]

We just released 2.4.0 Beta 3

@Lonsdale201 - we added option Remove post from current listing to allow users control - remove this post from current listing grid on deletion from store, or keep. Remove logic you need for wishlist-like stores, keep logic is suitable for your case with Likes

@dennylai1990 - we added fix for JetPopup and Listing compatibility and background color option for added to store link

You can download Beta3 from your Crocoblock Account

[Lonsdale201]

We just released 2.4.0 Beta 3

@Lonsdale201 - we added option Remove post from current listing to allow users control - remove this post from current listing grid on deletion from store, or keep. Remove logic you need for wishlist-like stores, keep logic is suitable for your case with Likes

@dennylai1990 - we added fix for JetPopup and Listing compatibility and background color option for added to store link

You can download Beta3 from your Crocoblock Account

You are too OP! :)

The "we added fix for JetPopup and Listing compatibility" is equal to work now, to use the add store dynamic link widget at the same time with the Jetpopup listing option? ( above i said, if the jetpopup option ebale on the dynamic link widget and that widget is a add store option, the add store function cant process, only the popup will work. I'm just curiosity. T

[MjHead]

@Lonsdale201 Yes, it works, but you need use it not in usual way but with this option - http://prntscr.com/sq1cr7, then you need to select popup in JetPopup section and set Trigger type to None

[Lonsdale201]

@Lonsdale201 Yes, it works, but you need use it not in usual way but with this option - http://prntscr.com/sq1cr7, then you need to select popup in JetPopup section and set Trigger type to None

Awesome. Now i uploaded the beta3, and now recorded a video. The cpt post broken on the backend. I guess i going back to beta 2, hope that resolve this issue for the moment. Can you send an email address? I uploaded the video, I'd like to show you to check this.

[Lonsdale201]

Ahh, nothing, i founded your email address. I shared the video with you.

[rousarp]

I like your plugin :-) 1) The "New post" form in the user dashboard inside Tabs does not work properly. I wanted to have a form for inserting new posts in the user dashboard inside the tabs. https://prnt.sc/sq8bde Unfortunately, inserting an illustration image does not work for me. Although the image is loaded, after submitting the form, it reports an error that this field is required. A separate page with only the form works correctly, a separate page with tabs and inside with a template with the form also works correctly. The problem only occurs when I insert it into the template for the user dashboard.

2) Error message The field is required. and Maximum file size: could be in messages settings in form setup for their modification, so that it is not necessary to modify the translation in the plugin itself. (2.4 Beta 2)

[rousarp]

It would like a better format in BE (editing CPT records) for related fields. Long names overflow the box. https://prnt.sc/sq8sf9 - I know it's a trifle that doesn't matter functionality, but still :-)

[dennylai1990]

We just released 2.4.0 Beta 3

@Lonsdale201 - we added option Remove post from current listing to allow users control - remove this post from current listing grid on deletion from store, or keep. Remove logic you need for wishlist-like stores, keep logic is suitable for your case with Likes

@dennylai1990 - we added fix for JetPopup and Listing compatibility and background color option for added to store link

You can download Beta3 from your Crocoblock Account

You're awesome! Tested it and it works! However, i found another bug. If i enable "Open popup on success" on the dynamic link widget, it does not pull the fields in the popup. Test it here. https://bit.ly/2yJxb6m. Click on the save icon and it should trigger the popup. I'm using the exact same popup on the same site here (It's the one that's just fixed. Popup button only viewable on mobile view) https://bit.ly/3evXg82. It works there on the same site.

[Lonsdale201]

Fuh..

Well i trying everything but, the full backend cpt posting system shut down. (beta2, and Beta3 tested) Trying to delete every conidion logic system in the meta boxes, Created new meta box, and deleting some. Change every number field to text. For now every time hit the publish button show: _/post-new.php?posttype=ingatlanok-2&wp-post-new-reload=true Any number click on the publish button on the backend just fill in more url strings.(the same)

[dennylai1990]

I found another bug on JetEngine v2.4.0 beta3. I deleted a custom post type and attached its post to another post type. Now, all the meta fields are duplicated for both the deleted post type and the non-deleted one. When i add a new meta field, the deleted post type gets it too. https://prnt.sc/sqcgyg From the image, you can see that the meta fields is duplicated both for "triggers" and "Stocks". "triggers" is my old cpt which i have deleted. "triggers" should not even be there anymore.

[Deswegen]

Would it also be possible to have taxonomies linkage available as field types for cpt's? Would like to have the possibility to move the taxonomies input of posts from the right-side menu and place them as checkboxes (generally different field types for the input, e.g. dropdown, radio-button options would be great) to other meta input. Here a screenshot: https://imgur.com/iOB4ZSy

[MjHead]

@Lonsdale201 we trying to reproduce the bug by your video and still can't, maybe its some specific issue. Could you please send me access details to your website with email to check this?

[MjHead]

@dennylai1990 Thanks! As for popup - click after submit calls popup without clicked post context. This was done b6 reasons That in most cases people will trigger popup with listing grid with saved posts, but I understand your point and we'll think how to combine old behaviour for plain listings and new for stores. As for meta boxes - we'll fix this 🙂

[MjHead]

@rousarp Hi! Thanks for reporting! These issues aren't directly related to 2.4, so we check them and try to fix with 2.3.7 release, because 2.4.0 will be available only in few weeks

[MjHead]

@Deswegen Taxonomies UI is rendered by WP core, so we don't have huge impact on how it will look like, but we'll research this issue, maybe find some solution 🙂

[Deswegen]

@Deswegen Taxonomies UI is rendered by WP core, so we don't have huge impact on how it will look like, but we'll research this issue, maybe find some solution 🙂

Alright nice, maybe have a look at ACF for inspiration, they seem to have found a way.