Digital experiences for all disciplines
Forum Replies Created
-
-
This reply has been marked as private.
We have version 2.0.8.
I’m bringing this one back up, as we are having a similar issue again.
One of our editors was working on a post (post ID 45750) and no matter what we did, the “Remove Article Pagination” under Post-Meta kept unchecking itself after saving the draft. This setting just wouldn’t stick.
-I tried one of my previous workarounds (copying the code from the Classic Text Editor, and saving as an empty Swift page builder page), and that did seem to work (the checkbox sticked). But after pasting the code again and saving the draft, the checkbox just unchecked itself.
-Another workaround was not to work in Swift Page Builder, but just making adjustment in the Classic Text Editor, checking the metadata box, and saving. That DID make it stick BUT then the lay-out columns got extremely squeezed in the preview of the post. So that didn’t do the trick either.
-So finally I went looking for the “asset” that triggered this bug of “unchecking the metadata box”. And after some research I found it: the Blank Spacer in our CTA row. I removed that one, checked the metadata box, saved, and IT WORKED. The box checking “sticked” and the lay-out was OK. I did some additional testing, and it seems that adding the Blank Spacer to this blog (doesn’t matter where: inside or outside a column or row), makes that metadata box go “rogue”.
Any thoughts on the cause or a possible fix?
I’m going to politely disagree with you. Your method makes it extremely difficult to trace file origins, much less being able to alter functions.
Putting all functions in the top level functions.php file and commenting to designate how and where they are used should be just as easy as ‘organizing’ them into separate files and subfolders.
You say
“unless people knew the name of the function they wanted to change, then they would struggle to find it. “
Well, I think it’s MORE of a struggle to find functions when they’re NOT in the functions.php file. If you have a single functions file, someone looking for a function has several options for searching (by function name, by parameter, by keywords they can find using web dev tools, etc) AND they have the confidence of knowing the function they’re looking for is in that file. Not only that, but they can easily change the function in the child theme.
As it is now, you have to use a tool like EasyFind (for Mac) to search through all the theme files to locate the function you’re looking for.
In any case – I wanted to reply to this with my own thoughts so that others may see there are different and possibly better approaches to doing things than what theme developers deem ‘right’.
This reply has been marked as private.This reply has been marked as private.I’m still having a serious issue with this. I’m having the same issue as @shism2 where, if the SPB has more than 11 rows, the post won’t update the meta options or WordPress SEO settings.
I updated to v2.0.8 of the theme. I updated to WordPress 4.2.2. I updated all the plugins.
I then did a deactivate and reactivation of all plugins – no change.
I disabled all plugins other than Swift Framework – no change.
I switched between Cardinal Child and Cardinal – no change (then switched back again).
I searched mercilessly for other solutions – nothing really applied.
I perused the database to see if anything looked out of order – I didn’t find anything.
I duplicated a problem post, removed rows from the SPB until there were only 11 left – that worked.So it appears that the problem is with SPB or the Swift Framework.
My next reply will have login info so you can take a look around.
OH – one more thing. I’m getting this error in my debug.log even though everything seems to be in the right place:
[29-May-2015 00:24:10 UTC] PHP Fatal error: Call to undefined function sf_aq_resize() in /wp-content/themes/cardinal/swift-framework/content/sf-post-formats.php on line 1009
Which version of the Swift Framework plugin was it added to? I’m assuming it’s part of the theme files – we’re on 2.0.2, so does that include it?
Can anyone tell me exactly where to put the code from @shism2’s solution?
I’d like to know the line number (we’re on Cardinal 2.0.2) with info about the code in the previous and following lines, for good measure.
We also recently ran into this issue. Is @shism2’s solution viable?
I had done some research and came across this post on the WordPress forums that seems to be related. It appears that posts without a ‘template’ have an issue with meta data not being updated. I’m assuming that this may apply to using the SPB, as there’s no template for posts:
https://wordpress.org/support/topic/plugin-does-not-let-me-save-seo-settings-on-pages
Here’s the text of that post, for good measure:
“The problem is the _wp_page_template in the wp_postmeta table. This was being saved to a previous themes template name.
You can change the following line of code in wp-admin/includes/meta-boxes.php:if ( ‘page’ == $post->post_type && 0 != count( get_page_templates( $post ) ) ) {
on line 742 to the following:
if ( ‘page’ == $post->post_type ) {
This will force the page attributes to display “Default Template”. When saving the page this will then update the value in the DB.
The actual line which causes the problem is: $page_templates = wp_get_theme()->get_page_templates( $post ); which is in wp-includes/post.php. This returns blank and then fails to run update_post_meta();”
We’re suddenly having the same issue. I think it may be because of an interaction with WordPress code and the theme. The gist is that, since Cardinal does not have any theme ‘templates’, the metadata is not being saved.
Here’s a thread that explains it further:
https://wordpress.org/support/topic/plugin-does-not-let-me-save-seo-settings-on-pages
“The actual line which causes the problem is: $page_templates = wp_get_theme()->get_page_templates( $post ); which is in wp-includes/post.php. This returns blank and then fails to run update_post_meta();”
The question here is – how do we fix this (if it’s actually the issue)? Obviously changing the WordPress code is not a viable option.
March 8, 2015 at 4:58 am in reply to: RSS Feed problem – not showing full content, only excerpt #155752On that same note – what is the function “/* FEED CONTENT WHEN PB ACTIVE” in sf-functions.php doing? It looks like it’s putting the Custom Excerpt into the RSS feed, rather than the full content of the post.
One more – what is the “RSS Feed URL” in the Theme Options panel meant for? What is it doing?
I’m just looking at all angles for why this problem is occurring. I’m testing in Feedly, just for reference.
No, no I wouldn’t. Putting the function in the root functions file, rather than nesting it in folders, would only make it easier to trace where functions are being generated.
If I copy that function to the Child theme function and modify it, then update the primary theme, the function is still there and nothing is lost.
So I’m a bit unclear where your answer came from. I guess I need to be more clear – why are these functions in nested folders, rather than in the root functions file? I’m really curious, as it seems to add an unnecessary level of complexity.
I have to ask – why would you do it this way, instead of putting it in the base functions file?
Yes, there’s a way to use code to call the Disqus function, the question is – how do we do it in such a way that it can be used in the Child theme?
The bigger problem is not being able to use files in the Child theme directory and have them take priority over the primary theme files. If you can tell me how that is done with this theme, putting the Disqus code in the proper place should be trivial.
-