Enis
Forum Replies Created
-
It worked like a charm for me, @nerrad
Thanks!
Same here. Upgrading to PHP 7.1 didn’t help.
- This reply was modified 6 years, 7 months ago by Enis.
Thank you, @klhall1987.
I’m looking forward to the new release.
Forum: Plugins
In reply to: [Glossary] Entry full content on archive pageIt worked ??
Thanks a lot! ^_^
Forum: Plugins
In reply to: [Glossary] Entry full content on archive pageI’ve disabled all the plugins, the theme and left just genesis, bare.
The problem persists.
Forum: Plugins
In reply to: [Glossary] Entry full content on archive pageThe theme I’m using is called “themecore”.
You can find it here: https://github.com/bradpotter/themecore
Meanwhile I’ll try disabling all the other plugins.
Forum: Plugins
In reply to: [Glossary] Entry full content on archive pageI edited /public/includes/Glossary_Genesis.php from line 41 to line 60 this way:
if ( is_singular() || genesis_get_option( 'content_archive' ) ==="full") { $content = get_the_content( get_the_ID() ); if ( is_single() && 'open' === get_option( 'default_ping_status' ) && post_type_supports( get_post_type(), 'trackbacks' ) ) { echo '<!--'; trackback_rdf(); echo '-->' . "\n"; } if ( is_page() && apply_filters( 'genesis_edit_post_link', true ) ) { edit_post_link( __( '(Edit)', 'genesis' ), '', '' ); } } else if ( 'excerpts' === genesis_get_option( 'content_archive' ) ) { $content = get_the_excerpt( get_the_ID() ); } /* if ( is_archive() ) { if ( genesis_get_option( 'content_archive_limit' ) ) { $content = get_the_content_limit( ( int ) genesis_get_option( 'content_archive_limit' ), genesis_a11y_more_link( __( '[Read more...]', 'genesis' ) ) ); } else { $content .= genesis_a11y_more_link( __( '[Read more...]', 'genesis' ) ); } } */
in particular, line 41 becomes:
if ( is_singular() || genesis_get_option( 'content_archive' ) ==="full") {
and the lines from 54 to 60 are commented, since Genesis takes already care to add the “[read more]” link.
This solves the problem.
However, some shortcodes and twitter cards are not rendered.
Forum: Plugins
In reply to: [Glossary] Entry full content on archive page@mte90, I’ve looked into this matter and apparently it’s glossary that makes my theme behave in an awkward way.
Keep in mind that I’m using a Genesis child theme: something robust and well coded.
Blog page and all the archives do not show the full content unless I set a very high character limit in the Genesis->Theme Settings page. They either show:
- the excerpt with the “[read more]” NOT linked to the article—that happens if I set “Display”->excerpt—or they show part
- all the content with a “[Read more]” link if I set “Display”->entry content and “Limit content to”->some high number text.
If I set “Limit content to” to zero, I get neither any content at all nor a “[read more]” link, whereas, if set to zero, this option should set Genesis to display the full entry content in blog and archive pages.
I tried deactivating all the plugins and switching to Genesis default theme and the problem persisted.
- This reply was modified 7 years, 5 months ago by Enis.
Forum: Plugins
In reply to: [Glossary] Entry full content on archive pageYou are right. It’s my theme doing strange things.
Thanks!
Forum: Plugins
In reply to: [Glossary] settings not accessibleOh, ok ??
Thanks
Forum: Plugins
In reply to: [Glossary] settings not accessibleSure, here you go: https://imgur.com/yjupun2
Furthermore, there’s no entry in the “settings” menu entry:
Has it ever been an entry, there?
- This reply was modified 7 years, 5 months ago by Enis.
Forum: Plugins
In reply to: [Glossary] settings not accessibleI see. Now it says “Cannot load glossary”
Forum: Plugins
In reply to: [Glossary] settings not accessibleMy plugin version is 1.3.6.
I’m an admin.I wonder if a setting page ever existed or if it’s just the wrong link on the “plugins” page linking to /wp-admin/options-general.php?page=glossary-by-codeat.
Please, do not mark the topic as resolved unless it is resolved.
The problem persists and it is NOT resolved.
I’ve proposed an edit on your github.
https://github.com/wpninjas/ninja-forms/pull/2787
That edit fixes this issue.
I’ve just filed a pull request in your github, where I minified the offending js.
https://github.com/wpninjas/ninja-forms/pull/2787
That edit solved the issue.
Your call.