Code Amp
Forum Replies Created
-
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Custom Field Not Pulling InHey @imavexadmin
Apologies for the delay – that is odd indeed.
How are you creating your custom fields?
Our plugin doesn’t do anything special with custom fields, it just fetches the field using the key you supply – we use the WP function
get_post_meta()found here:
https://developer.ww.wp.xz.cn/reference/functions/get_post_meta/Therefor my best guess would be, that when saving your post (the event that seems to cause them to go missing), they custom field is being saved under a different name / in a different format.
If you are using a pluign to create your custom fields, it is possible it has been updated, and might be doing something different than what it used to.
I would try to figure out if the custom field name (meta key) has changed, and try the new custom field in your post template.
If you’re still having issues, we’d need to take a closer look at your site – in this case can you open a ticket with Search & Filter support?
Search & Filter + Custom Layouts are the same team, that way we’ll be able to access your site and have a look at whats going on (be sure to reference this ticket).
Thanks
- This reply was modified 3 years, 9 months ago by Code Amp.
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Sticky posts onlyHey @kaichi
You can use our
query_argsfilter, to modify the query, found here:
https://customlayouts.com/documentation/action-filter-reference/And combine it with the info from this stack exchange post:
https://stackoverflow.com/a/19814472/459359And you should end up with code that looks like:
function layout_query_args( $query_args ) { // Get sticky posts from DB $sticky_posts = get_option('sticky_posts'); if ( ! empty( $sticky_posts ) ) { // Modify the query $query_args['post__in'] = $sticky_posts; } // Always return in WP filters return $query_args; } add_filter( 'custom-layouts/layout/query_args', 'layout_query_args', 10 );Note- I didn’t get to test this – but in principal everything looks correct.
Best
Forum: Plugins
In reply to: [Search & Filter] Plugin won’t work with PHP 8.0Thanks for flagging.
This was an issue in the pro version of our plugin, and was patched some months ago.
The solution is to update the plugin, we’re now on v2.5.13.
@zecompadre let me know if you’re seeing the same.
Best
Forum: Reviews
In reply to: [Search & Filter] Life and time saverAwesome thank you @pyho 🙏
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Sticky posts onlyHey @kaichi
I’ll put this as a feature request and hopefully we can get this added.
If you are comfortable with a little PHP and WP actions + filters, I can point you in the right direction to achieve this (without waiting for our update)?
Thanks
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Custom Field Not Pulling InHey @imavexadmin , it looks like you are having an issue with our Search & Filter Pro plugin?
Can you open a ticket with S&F support?
https://searchandfilter.com/You can open a ticket via your account and there will be someone ready to help!
Best
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Issue with Search & FilterHey @emgb_520 – this will be released next week.
Best
Forum: Themes and Templates
In reply to: [Blocksy] Editor console warningStrange, without explanation, the error has dissapeared…
I dismissed the notice, then deleted the option (for the dismissed notice) from the options table, and now I can’t reproduce.
My best guess as to why maybe this notice was triggering was I was creating posts using a plugin that generated them for the classic editor.
Anyway, I’ve see you’ve closed this, and I can no longer reproduce, so probably best to leave it that way!
Cheers
- This reply was modified 3 years, 9 months ago by Code Amp.
Forum: Themes and Templates
In reply to: [Blocksy] Editor console warningHey @cteduard
So I tested it on a clean install, and didn’t see the issue immediately upon going to the editor.
I did delete blocksy and re-install on my dev (pretty clean) install and the issue came back.
Switching to another theme made the issue go away.
I’m not 100% sure what’s causing this, this install doesn’t have any plugins enabled or custom code running.. And it is only a warning, not an error.
But still I’m curious… Looking at the bundled JS file:
themes/blocksy/static/bundle/32.6b6e363eda9a039182ed.jsI can see
"fill-rule": "evenodd", and if that is being used in a React component as a prop (it looks like it is) then the warning imo is valid, a React component should have the propfillRuleinstead (on the SVG I’m guessing).Anyway, I’m not sure the conditions to replicate the warning, but my guess is based on looking at the code, the warning is valid…
Not sure that helps a lot!
FYI, I am just testing Blocksy (amongst other themes) for compatibility with a plugin I’m building.
Thanks
- This reply was modified 3 years, 9 months ago by Code Amp.
Forum: Themes and Templates
In reply to: [Blocksy] Editor console warningHey @cteduard
This is just on my dev environment. I double checked with the following setup:
– Latest WP
– No plugins enabled
– Blocksy theme
– Sample content generated from FakerPress plugin (and disabled)Here is a video:
https://drive.google.com/file/d/1R61Nugd4npS9GBK7D9QvkXRSKKsZD9Ue/view?usp=drivesdkThanks
Forum: Plugins
In reply to: [Contact Form 7] JS errors/conflicts and forms not working after updateHey @mhair
Sounds like you might have got the name mixed up but based on the version numbers you supplied I assume we’re all talking about Search & Filter Pro.
It sounds like your assumption is correct, in order to use Search & Filter with the latest CF7 you’ll need to update your copy of Search & Filter to 2.5.13.
Thanks
Forum: Plugins
In reply to: [Contact Form 7] JS errors/conflicts and forms not working after updateHi all, we released an update with a fix for this last Thursday.
The issue was we were using an old polyfill for the JavaScript function
String.replaceAll()Since this is now supported by all modern browsers, the solution was to remove this from our codebase.
@peps23 you might want to check which plugin is causing this issue, and if it is exactly the same then you can contact the plugin/theme author with this information. IMO this specific issue (where the error comes from the use of
replaceAll()) is not a bug with CF7.Thanks
~ RossForum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Margin and paddingThanks for the feedback.
Yeah the gap is currently only one size.
We’re holding off a little on the responsive options until we see what direction Gutenberg takes – so we can keep in sync with their UI (they have some open github issues about this sort of thing already / in progress)
If nothing happens in the next few months we’ll surely start rolling out our responsive UI (like you get with the number of columns) to a bunch of other settings.
Thanks
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Margin and paddingHey @xmarksthespot
I managed to figure this out:
.cl-layout { margin-left: calc( var( --cl-layout-spacing ) * -1 ); width: calc( 100% + ( var(--cl-layout-spacing) * 2 ) ); } .cl-layout:not(.alignleft):not(.aligncenter):not(.alignright):not(.alignwide):not(.alignfull) { max-width: calc( 100% + ( var(--cl-layout-spacing) * 2 ) ); }I’m putting this on the todo list for the plugin, I think we will switch to CSS Grid and solve it withing the plugin at some point in the future.
Thanks
Forum: Plugins
In reply to: [Custom Layouts - Post + Product grids made easy] Issue with Search & FilterHey @taeinkyun
We found an issue where the search form would connect, but when you edit the custom layout, the option (search form selection) would reset to the first choice.
We fixed this in our beta:
https://customlayouts.com/documentation/beta/Thanks