Forum Replies Created
I did not even know about this plugin.
When I buy the package, I paid for you and not for this Unsyon.
This response is unfortunate. I see that I paid for something I do not have support for.
I did not like One Click Demo Import method.
I prefer the Demo Content Install, because it cleans everything and leaves thema as the original. But need to fix the SQL Script to remove ENGINE = MyISAM
Only impromptu form that worked, go to Tools> Demo Content Install.
While the process happened, in shell command I kept repeating the execution of this command in the folder /wp-content/uploads/fw-backup
sed -i ‘s/ENGINE=MyISAM/ENGINE=InnoDB/g’ tmp/database.json.txt
I did the import as per the image, but had some nonconformities.
The menu has items from the previous theme, and the blog and gallery have retained some images from the previous theme.
What we can understand is that he could not clear the information from the previous thema.
I was with thema construction and import to boxed.
Here you are also presenting this error.
<p class=”fw-text-danger”>Failed to create tmp table _fwbk_demo00_commentmeta. Storage engine MyISAM is disabled (Table creation is disallowed).</p>
I use Google’s MySQL server. And by default MyISAM is disabled.
in the /wp-content/uploads/fw-backup/tmp/database.json.txt file I have removed the string “ENGINE = MyISAM”, but every time I click the install button of the Demo Content it downloads and updates the file with the string “ENGINE = MyISAM”.
The google recommendation is this:
You can avoid this error by removing the
ENGINE = MyISAMoption from theCREATE TABLEcommand. Doing so creates the table with the InnoDB storage engine.So, any solution to this?
Thank you!
I’m a developer, yes. If you observe you will see that I have reported several errors of thema for you. View all posts from my profile.
I just want to know the ways to make the change. I’ve already made several changes using the child theme.
I know that just customize the CSS to overlap all TAGs H1 and H2. But I’d like to customize by adding in the combobox in the style customization tab of thema.Can you guide me which files to change?
I did just that. I copied the entire parent theme directory to the child theme directory.
copy jevelin/inc/widgets/image/* to jevelin-child/inc/widgets/image/
How do you work? Did you this test I did?
I want to add a font of mine, totally customized.
I know it’s possible to add via CSS. But I would like to make a more elegant way … that the added font would appear in the style asbobox in the theme settings.Hello!
I do not confuse. I did the test exactly with “Shufflehound Information” in the directory: jevelin/inc/widgets/image/Better saying in the child’s thema’s directory: jevelin-child/inc/widgets/image/views/widget.php
Take a test there for you to see. I needed to remove esc_attr to allow HTML code.
thank you so much
thank you so much
I was able to change the custom post type using the child thema.
But using the link method (http://wpsmith.net/2013/use-registered_post_type-hook-to-modify-post-type-registration/) you indicated did not work well.The code I used, was this:
add_action( ‘init’, ‘edu_remove_prefix_blog‘, 999);
function edu_remove_prefix_blog() {
$obj = get_post_type_object(“fw-portfolio”);
$obj->rewrite[“with_front”] = false;
$obj->rewrite[“hierarchical”] = true;
register_post_type($obj->name, $obj);
}Can you tell me if it was the right form? If not it will overload my site.
There was a new update for version 2.4.10
The changes I suggest did not appear.Do you have any idea which version will be updated?
Thank you!
OK.
Thanks for the answerOK. Thank you!
I’ll try to use the theme child.Just install it normally as if it were a thema. Right?
Can you guide me where to put this code?
OK. Because of the name I imagined it was created by you.
Is the code using hook to modify custom post type added in the functions.php file of thema?
Thank you!
I’m waiting for correction as soon as possible.Thanks for suggesting the change to the developer.
But I have a question.
This file (/wp-content/plugins/unyson/framework/extensions/portfolio/class-fw-extension-portfolio.php) was created by unyson and not by you?I’m suggesting an improvement for thema.
Because the way it was implemented is this “wrong”. Take the Custom Post Type products from woocommerce as an example. It did it correctly and it works without me having to change anything.
This improvement will not affect anything in thema and will still work better. Because custom Post Type is not part of the BLOG structure.
