Forum Replies Created
-
Posts
-
Ok…for me it fixed the issue…but it has made ALL products show that they are out of stock, even if there is zero stock management on the product…
I know it’s been a bit since the last update, but I think I covered most of the stock WooCommerce elements, plus a few other goodies. That said, there are a LOT of WooCommerce and WordPress plugins out there that are really popular. If anyone has any requests for smaller elements for popular plugins….as in ones that use shortcodes…share the link here. If I have the time and will to live….I’ll occasionally include some in updates to come. If there are more complicated plugins or some nice CSS/HTML elements that you use and would like converted to an element, contact me directly via my site for a custom quote.
Thanks!
That I honestly don’t know. 500 errors are usually on the server side. Not knowing what your server setup or WordPress install looks like, I couldn’t tell you what the issue is. All I can recommend is to delete all the files, then make gradual edits. Start with the code in your functions.php file and double check to make sure nothing is missing. Then add the shortcode files one at a time to see if one of them happens to not play nice for some reason. I’ve never had this happen on my few dozen installs and no one else has mentioned having this issue.
MINOR UPDATE
Just cleaned up some of the code. As there was a LOT of WooCommerce elements, I moved them to their own tab. Hopefully, @Kriesi can make a minor update to their shortcodes to have all of the WooCommerce ones go into a WooCommerce tab as I have done in this update. I just feel it makes better sense to keep things organized and easier to find.Now…that said… Any element requests? For instance, any nice CSS snippets you’ve found? The ribbon element is an example of something that uses only CSS. The color picker would be an example of a simple element that uses CSS and a little javascript. If I happen to like any, then I’ll consider putting them together.
You can also contact me directly via my website in regards to creating a custom one for you.
Well… For those still experiencing this, the WP admin logins won’t work. This breaks both the front and back end. But the error message that comes up is in regard to the shortcode handler. A PHP upgrade fixes it. I’d assume most of those who had this issue have fixed it. Maybe there are some who haven’t though.
It’s the PHP version your host is running. Needs to be 7.1 or higher. The devs included something in this update which requires that. They should have tested it and had that in mind, but for whatever reason they didn’t consider that some people might not know.
Your options are to manually update the PHP version, ask your host to update it, or revert back to the old version of Enfold and wait until the release a patch update.
For those still suffering from this issue… If your host doesn’t allow you to update the PHP version, contact them asking them to do so. If your host, for whatever odd reason, doesn’t run a newer version of PHP, ask them to roll back the site to a backup. If you aren’t running backups, then try to find the prior version and re-install Enfold.
Until the devs add a warning like we see in other themes/plugins, or until they rollout a fix which will not kill your site…those are your only options sadly.
…and queue the ego trip. If this wasn’t an example of a “Bye Felicia” moment, I don’t know what is. Try giving advice without first demeaning people.
@Yigit – That is clearly the problem, but the underlying issue is that there was no warning that a new feature was added that requires 7.0 or higher for PHP. Yes, it’s a good idea to keep the PHP version updated, but it’s safe to say that many wouldn’t know how to do that and some hosts don’t have a way for users to manually do so. Combine that with the fact that many hosts for WordPress sites have automatic updates for WP, plugins and themes…this can and has shown itself to be an unexpected issue…a major one at that since it is taking down sites completely.
The devs knowing that they were updating something in the theme which specifically requires php 7+, they should have included either a check on that which would have loaded a legacy failsafe, or at least included a warning the same way other plugin/theme devs do.
If the devs can, they should halt the update rollout and make the previous version available for download in some manner…themeforest if they allow a rollback. Then take the time to fully test out this version. Like it or not, Enfold did work on older versions of PHP, so it isn’t unreasonable to assume some users still have an older setup.
Well that was a rude response. Couldn’t craft a response that was mature and considers the many scenarios and setups other users may have? You do realize that some novice users might not know how to update it or even be able to discern that the PHP version is the issue? That every host has a different process? That some hosts don’t keep their phone versions updated? That some people have automatic updates turned on and may bot know this will kill their site and affect their businesses? No need to degrade others.
When updating a plug-in or theme will literally kill the website unless a specific change is made beforehand, it really helps to give uers a heads up. Other developers seem able to include such update notices. I was able to fix that for my clients by updating the php version. The devs knew they were using a new version of the shortcode handler which requires the use of a newer version of PHP. I find it hard to believe no one there thought there wouldn’t be any issues. If they aren’t doing tests on different setups and aren’t putting in fail-safes, then they need to tighten the screws. Notices of potential update issues is literally the least any established dev can do.
Why hasn’t any of the team addressed this? This is a MAJOR issue. Several sites are down now because of this issue.
Why is this update still being pushed out when some many sites are going down because of it? I have client sties down now and there doesn’t seem to be a fix.
UPDATE
– Few minor updates made to several elements to clean up the code.
– Updated the “Category Promo” by removing it and replacing it with a straight up “Product Promo” that will allow you to make the promo about a single product or a product category. It has a lot of options built into it to cover just about everything. While it pulls a lot of details automatically from the product or category, I’ve made it so you can override and customize each aspect.UPDATE
– Minor fix to all elements to ensure that when you tick an option to hide the element based on screen size will actually hide.
– Updated the Modern Product element to include a corner badge indicating that the product is NEW if it is 60 days or newer. Can be enabled/disabled and the colors for the text & background can be customized.
– Added a new element, Ribbon Header. Displays the heading text of your choice over a flat style ribbon. Can be fully customizable in terms of text size, font color, and ribbon color.
I think I figured out the problem…not a solution…but the problem. The code creating the preview pane is doing so with an iframe and it is difficult to pass css onto a generated iframe. So my lil hack will have to do for now I suppose…at least until someone comes up with a creative idea for getting it to work. Maybe some kind of hook that plugs into that file.
I don’t know how else to explain it. Your example modifies the CSS of the preview pane itself. That is in no way what I’m trying to do. The preview pane does not load the CSS for the element itself. The only way I have been able to get it to do so is via editing that core file or copy/pasting the entire style sheet into the quick CSS. Hell, the quick CSS box doesn’t even respect a simple @import line to do so.
Again, the element loaded in the preview pane, not the preview pane itself.
In your example, you changed the CSS for the preview pane itself. I’m talking about CSS for the custom element. So you get a live preview of it as it would look on the front end. I’m bit trying to modify the preview pane itself. Just want to have it load the CASE that applies to the element.
I did, but like I said, it didn’t work. I simply copy and pasted the code you shared, then changed the name of the css file. It failed to load it in the preview pane.
Is there a specific place in the custom element file that it needs to go? You gave some code, but didn’t say where in the file it must go.
FYI…these forums are in desperate need of an update. They are terrible on mobile. Just saying…
Is there an updated version of this that is responsive? I’ve tried the code in the theme documentation…but to be honest, it’s kinda sloppy/lazy. Yes, it allows you to add a widget to the header, but it doesn’t stay in line with anything once the size of the window changes and in mobile view, it just overlaps anything there. I’m surprised that something better hasn’t been baked in to account for a layout where you have the logo on the left and the menu below. It leaves all that space on the right that is prime space for things like a call to action. The available hooks don’t seem to work all that great. Even this one doesn’t allow for you to align the widget to the right and keep it within the max width settings for the content.
BIG UPDATE
– Feature List updated to be a single element similar to the icon list element. New options based on use and updated to better account for a responsive layout.
– New product image option Modern Product Image. Gives a minimal look with a nice hover effect.
– New single product element Modern Product full of great premium options like sale tags, extra feature highlight, gradient overlay effect, etc.
– New Copyright element to always display the current year. Optionally include a start year and additional text.
– New Product SKU element to display the current product’s SKU.
– New Product Price element to display the current product’s price which can be placed anywhere. Includes some premium style options.
– New Edit Link element to display a button that will take you the current post type’s edit page. Only displays if the current logged in user has edit capabilities.Side note…
I did make this a paid addon due to all the time that has gone into it and new premium features, but it’s only $10. Given all the elements and future ones planned, I believe it is a fair price for premium elements that only extend the versatility of Enfold. Pay once, then you get all the future updates. Recommended that you create an account to ensure you have access to the updates.But where does that snippet need to be placed? I tried placing it in the element file itself…that didn’t work. The CSS file is in there. using the same enqueue code independently it loads fine on the front end of the site.
wp_enqueue_style( 'spiderfly', get_stylesheet_directory_uri() . '/shortcodes/css/spiderfly.css',false,'1.1','all');
If I don’t also edit the core file to call the CSS, it won’t work in the preview pane.Now, if I mod your code to reflect where the CSS file is, it does not load on the front end nor the preview pane.
To be clear, I am placing this, and my, code in the custom element file itself, which should work as any other function I’ve used has worked fine. Seems like calling the array in there is what it doesn’t like.
Unfortunately, that didn’t work. It failed to load the CSS completely. Is there a specific place where it needs to be placed in order to work?
If anyone is interested in seeing a live version of the upcoming addition… https://www.spiderflystudios.com/resources/spiderfly-enfold-elements/
As mentioned, I won’t make it live until I can figure out a better way to make the CSS load in the Enfold preview pane. Once I do, I can begin expanding the design to include posts, arrays, etc.
Update – I found where in the template-builder.class.php file where I need to add the CSS. That works, but I can’t ask people to edit a core file…not gonna get in that mess. I also tried doing a simple @import line to just import the contents of the css file into the quick css…that didn’t work.
Still looking for an easier way…
After some testing…I can’t see myself uploading these new updates until there’s a good way to get the CSS to load within the preview pane without having to have users copy/paste it into the quick CSS box. With the more complex elements that I’m trying to make, they almost need the preview for expediency.
Update – I tried baking the CSS into the element and that didn’t even work completely. Seems like the only way to get all of the CSS to load completely within the preview pane is to copy/paste all the CSS into the quick CSS box of the theme settings. If more devs are going to create custom elements for Enfold users, then there needs to be a better way to get the CSS loading properly for previews.
