Forum Replies Created
-
Posts
-
Hi Ismael,
Is this a known issue since the October 5, 2020 Enfold 4.7.6.4 release?
When is the next release with the fix?
Thank you.Hi Ismael,
Thank you for your detailed response.
I was simply going to search the wp_postmeta table and remove any instances of wp_old_slug and any instances of WP_old_date.
Is your recommendation to add your code to the function.php file?
I read the remarks in your code. Can you please explain what it is really doing?
Thank you.Please remember to include the latest version of LayerSlider WP in the upcoming Enfold update.
Thank you.Hi Basilis,
The FTP details were in the private data on the top of this post.
Rikard’s suggestion to add the Envato token to the child theme (see above) has removed the error in the child theme.
Thank you both!Please close this thread.
Hi Rikard,
Now that you have confirmed that the “child theme will never be overwritten on updates”, I inserted the Envato private token and clicked “Check the private token”. And received the following message:
We checked the token on 2019/11/26 14:37 and we were able to connect to Envato and could access the following information…Line 93 of wp-content/themes/enfold/framework/php/auto-updates/class-pixelentity-theme-update.php is:
if ( ! in_array( $current->item_id, $purchased_ids ) )
I am assuming it was checking for the token in the child theme.Everything was working prior to adding the token. I just like everything working without errors or notices (like the fact that the LayerSlider in the Enfold theme needs to be updated again). You never know if an error or notice is causing a problem you just have not noticed yet. It’s always better to get ahead of these things. Hopefully, the error will go away after I confirmed the token in the child theme.
Thank you.
Hi Rikard,
Since it appears sometimes, I took a screenshot and placed it in private content below.
Were you able to see the screenshot?The reason I put the API key in the parent only and not the child is to avoid the child from being overwritten with theme updates.
Thank you.Hi Rikard,
Please see the private content for a screenshot of the error.
I added the token to the parent theme, not the child theme, in 2018. I update the parent theme, not the child theme, each time there is an update.Can you please help?
Thank you.Hi Rikard,
Yes, it has a url. Please see private content.
Thank you for the link on how to hide it, but I am interested in how to fix it.
The error in the backend of my admin: is related to Enfold:
Notice: Trying to get property ‘item_id’ of non-object in /var/www/wp-content/themes/enfold/framework/php/auto-updates/class-pixelentity-theme-update.php on line 93Thank you.
Hi Rikard,
I removed the header.php file in the Child Theme folder and helper-main-menu.php in the Child Theme includes folder.
They are no longer necessary after updating the Parent Theme to Enfold 4.5.1.
My site works great without them in the Child Theme.
Thank you.Please close this thread.
Hi Rikard,
I am not sure what you mean by ‘whatever reason’.
Why would my Child Theme and other users’ Child Theme (llike @medi-paper – see old thread link above) need the same 2 files already in Enfold Parent?
Please see my Private Content for my ftp login to better answer the question.
Thank you.Hi Rikard,
Moderator Ismael, said users need to manually “update the header.php and helper-main-menu.php file in the child theme folder after the upgrade“. With each Enfold Parent update, certain Enfold Child files need to be changed. The top of the support forum does not have a fixed thread of instructions on which files and path are needed to be manually updated in the Enfold Child when updating the Enfold Parent.
See:
update the header.php and helper-main-menu.php file in the child theme folder after the upgradeDetails for live site running Enfold 4.5.1 with WordPress 5.0 in Private Content below.
Please help. Thank you.Hi Rikard,
My concern is our hosting provider GoDaddy automatically updates everyday to the latest WordPress (full release).
I meant fully tested on WordPress Beta 3 in my original post.
If Enfold 4.5 is fully tested on WordPress 5.0 Beta 3 it’s probably almost/fully compatible with the final WordPress 5.0.User @crtdude said: “As noted elsewhere, other them devs have enabled a checkbox disabling the Gutenberg editor within their theme’s environment. I would expect Kriesi to do the same…”
Please see:
Enfold 100% compatible with GutenbergThe checkbox is a great idea!
Thank you.
Hi Yigit,
Thank you!
Can you please update future Enfold releases with the latest version of the LayerSlider plugin?Hi Mike,
I went back to my thread with a question. I’ll stop posting in this thread if you can please continue responding in my thread. Thank you!
Hi MIke,
Thank you for your help. Good catch.
I moved all the parent theme files and folders from wp-content/themes/enfold/enfold to wp-content/themes/enfold.
Then I deleted the folder wp-content/themes/enfold/enfold.
Then I copied wp-content/themes/enfold/header.php to wp-content/themes/enfold-child.
Then I copied wp-content/themes/enfold/includes/ helper-main-menu.php to wp-content/themes/enfold-child/includes.My Problems:
Enfold is not showing as a theme in Appearance>Themes.
Broken Themes lists Enfold Child “The theme defines itself as its parent theme. Please check the Template header.”
Can you please help? My revised ftp private details are below. I want to test everything on the staging site before moving it to the live site.
Thank you.I was able to update to Enfold 4.5 on my staging site, but now the Enfold Child shows up in Broken Themes on the Themes page.
My thread is here, but the responses have been a little slow.
Enfold 4.5 Update – Problem Enfold ChildBest solution?
You may want to the follow my thread as well, titled ‘Enfold 4.5 Update – Problem Enfold Child’:
Enfold 4.5 Update – Problem Enfold ChildHi Victoria,
All plugins are deactivated on the staging site with Enfold 4.5 as the parent.
Please see the live site link in the private details so you know what how the live site running Enfold 4.4.1 with the Enfold Child looks.
Thank you.
