[Resolved] Hello , i need help

[Author]

Posts

[JI-MANJ3427]

The following are the problems encountered with the current use of Toolset, organized as follows:

1.Added "Slug" for "Field", which cannot be the same as the deleted field alias.
For example, if you add a field with the name "event-title" at the beginning, delete the field and add a field with the same format or different format. The alias can no longer be named "event-title".

2.If the format of the "Field" is changed, the created post (Post) field displays an error message; if a new post (Post) is added, the field displays the new format item normally.
For example, if there is a field with the format of "Checkboxes" and some articles are built, after the change of the requirement is changed to "Wysiwyg", the content of the created article will display the error message; but if it is a new one In the new article, this field will normally display the new "Wysiwyg" block for editing.

3.How to use "Checkboxes" to display all items in the Post (Post), and determine the different CSS classes when "Selected" and "Not Selected".
For example, the items that can be selected are “big”, “medium” and “small”. The front desk also displays three items “big”, “medium” and “small”, and is CSS class="a"; When "big" is selected, class="b" is applied, but "medium" and "small" which are not selected are still class="a".

4.How to set the "View" item whose output condition format is "relationships" in "Layout".
For example, "Student" and "Classroom" are "relationships", and a "View" has been set to display the students in the class; "View" is inserted in "Layout", and the block is not displayed when there are no students in the class. Any content.

5.How to set the output condition format to "Categories" in "Layout".
For example, the article category has "A", "B", and "C". When [A] is selected, class="a" is selected, and when [B] is selected, class="b" is applied.

6.Image How to set a relative path to avoid path errors when forwarding.

7.When using the oceanwp theme, can the View of the Toolset inherit the paging function of the oceanwp theme? When the theme is currently applied, the original paging function does not respond to page switching.
For example, 10 articles are displayed on each page, and the 11th article is on the second page. When the second page button is pressed, the URL and button are displayed as the second page, but the content is still the first to the first page. Article.

[Beda]

Please use a new thread for each non-related issue:
https://toolset.com/toolset-support-policy/

In short, I can answer here but for details, please open new tickets each issue.

1. It is possible as soon as you head to Toolset > Custom Fields > Post Field Control and delete that field from the database.
Direct link: wp-admin/admin.php?page=types-field-control&domain=posts
2. Checkboxes Custom Field cannot be changed to WYSIWYG. Please if this issue is still happening to explain to us in a new thread how you manage to change the type of such a field once it's saved, as this is not possible in Toolset (see screenshot)
3. This is possible with several different approaches we can talk about in a new ticket, but basically, you will use an HTML condition that checks on the field value. If the field value is "xy" you would add a class "xy" to the DIV or any HTML where you use this to add later your CSS. Conditional HTML is elaborated here:
https://toolset.com/documentation/user-guides/conditional-html-output-in-views/
Similar ticket:
https://toolset.com/forums/topic/conditional-styling/
4. I don't understand this point, but Views to display related posts are usually set up as elaborated here:
https://toolset.com/documentation/post-relationships/how-to-display-related-posts-with-toolset/
In Layouts that does not differ because you would just insert the View in that Layout and still it would display what you set in the View. If the View works in a native WordPress Post it should also work when inserted in a Layout.
5. If you mean Toolset Layouts applied to a page or post, depending on Taxonomies (such as Categories), this is not possible without custom code. The same is valid for Content Templates. Such custom code cannot be provided by us but there are examples, such as https://toolset.com/forums/topic/set-specific-layout-on-specific-post-status/
6. Again I am not sure what you mean but if this is about the display of Images, or generically about any URL in the site, you can usually replace the "hidden link" part with [wpv-bloginfo show="url"] in an "a href", this ShortCode can be produced with the GUI of "Fields and Views". If you mean to display Images per se, such as a Featured Image, or any Toolset Types Image Field, you do not need to worry about the URL because it is managed by the ShortCode just fine.
https://toolset.com/documentation/user-guides/views-shortcodes/#vf-153425
https://toolset.com/documentation/customizing-sites-using-php/functions/#image
This sounds like a compatibility issue or maybe a wrong usage of an Archive View on an Archive that the theme offers.
I recently tested the OceanWP Theme and it worked great, I am also in contact with their DEV's, so if there are issues we can replicate, we are happy to solve them. However, we would need concrete steps or an example site, in a separate ticket.

Thanks!