- This topic has 15 replies, 3 voices, and was last updated 10 years ago by
.
-
Posts
-
With the former version of Ally, converting an existing site to HTML5 the hard way, I have most everything resolved except for the portfolio page which won’t follow the Genesis site settings for portfolio page – showing content limited to 200 characters.
Is there a line of code I should add somewhere to get my portfolio to respond to this setting as it did before?
Did you update the portfolio code in your functions file? I noticed that the code there and the portfolio file was all updated with the HTML5 function names.
Answer is “no” and that’s probably the missing line(s) of code. I don’t know what I should do. I could download the new version of Ally and start looking for differences but I’m not a PHP guru and am not sure what would allow the functionality I seek to return to while also not breaking the site.
@stinkykong I’ll try and help, do you remember when we were discussing the portfolio code in your functions file a while ago? The code at the bottom is what controls what shows up on the options page….and that code of course links to the portfolio template. Make sure and update (copy/paste) the code from your functions file and replace the older version…same thing with the portfolio template. Of course, backup all of your work just in case and error is made.
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
I do remember and did check that thread. That was regarding a missing segment of code from an earlier version of a different theme, Epik, which predated the changeover to Genesis 2.0 and HTML5 activation. In that thread’s issue, the choice of category selection was missing in the admin panel.
https://appfinite.com/topic/no-category-selection-in-portfolio-settings/BTW, I also checked to see that that particular code is present, plus more relating to the portfolio functions that came with Ally, in fact.
The issue here is different. It’s with portfolio page displaying full content rather than content limit and only since the activation of HTML5.
Yeah that’s why I mentioned the code in the functions file and the portfolio template itself. It has to be updated in order to work.
I can confirm that the new version does in fact work, I have it up and running with no issues.
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
Eric, sorry if I’m asking for things you don’t support. Can you post the specific code lines you’re talking about?
The code you mentioned in the thread related to portfolio (in Epik) is this
<p><?php _e("Display which category:", 'genesis'); ?> <?php wp_dropdown_categories(array('selected' => genesis_get_option('epik_portfolio_cat'), 'name' => GENESIS_SETTINGS_FIELD.'[epik_portfolio_cat]', 'orderby' => 'Name' , 'hierarchical' => 1, 'show_option_all' => __("All Categories", 'genesis'), 'hide_empty' => '0' )); ?></p>This was to have the category options display in the Genesis Theme Settings panel of the admin area. But that is working fine. That’s not what is broken.
I actually meant that entire section of code from the top to bottom needs to match the latest updated version. And then double check to make sure the portfolio template is exactly the same as the latest version as well.
I’m not referring to just that particular line of code, but the whole thing. The reason is because there were a few things changed for 2.0, and if you’re using the HTML5 markup and don’t add in all of the changes then it probably won’t work.
Is it possible for you to temporarily replace the entire functions and portfolio template with the new versions so you can see that it works? Then you could add in your other custom code manually and do a test each time to make sure none of it is conflicting with it. Does that make sense?
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
I just thought about something, are you just using Genesis 2.0 and the old child theme? Or are you actually using the latest HTML5? I just remembered that the code in the new files are only designed for HTML5 and not the older version of Genesis markup….but if you are using HTML5 and have it Enabled in the functions.php file then we should be ok. I just wanted to make sure we’re on the same page.
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
Yes, Eric, it is a “conversion” from the “former version of Ally”. Trouble is, we’re not ok since the portfolio page for some reason is not responding to the content limit I have set in the Genesis Theme Settings.
And I have tried what you suggested replacing “all the code” in both functions.php and in page_portfolio.php, but unfortunately that breaks the styling of all pages.
I really hope to find just the code that revitalizes the portfolio page’s ability to recognize the content limit. It did before the conversion and I would like to fix this issue.
Sorry, I’m not sure what you’re doing wrong. If you use the theme on a separate installation (local or another subdmain, etc) then you’ll see it’s working. I’m using the exact version as you (which is available in the downloads area).
On the settings page –
“Select one of the following:” is set to “Display Content”
“Limit content to” is set to 100 (as an example).
and this is the result – http://i.imgur.com/v23JGRs.png
That shows that its working. So it could just be some
If you’re wondering what code displays the option in the options page, it’s this –
<p><label for="<?php echo GENESIS_SETTINGS_FIELD; ?>[ally_portfolio_content_archive_limit]"><?php _e('Limit content to', 'genesis'); ?></label> <input type="text" name="<?php echo GENESIS_SETTINGS_FIELD; ?>[ally_portfolio_content_archive_limit]" id="<?php echo GENESIS_SETTINGS_FIELD; ?>[ally_portfolio_content_archive_limit]" value="<?php echo esc_attr( genesis_option('ally_portfolio_content_archive_limit') ); ?>" size="3" /> <label for="<?php echo GENESIS_SETTINGS_FIELD; ?>[ally_portfolio_content_archive_limit]"><?php _e('characters', 'genesis'); ?></label></p>That is from the functions file, and as you know, it affects what is displayed from the portfolio file.
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
I’m not sure what I’m doing wrong either. I need help from someone who can tell that. Is there someone there who can tell me that? If there isn’t, then I need to quit asking for help.
What do you mean you need to quit asking for help? LOL This doesn’t make sense, are you not following my suggestions? (doesn’t seem like it) Or did you not want the help from me or something?
“I’m not sure what I’m doing wrong either. I need help from someone who can tell that. Is there someone there who can tell me that?”
You do realize that NO ONE is going to KNOW what you are doing wrong, because you are the only one with access to your backend. It’s impossible for anyone to know what you’ve done wrong, and there is no way to help you other than guessing what it could be….and that’s “a shot in the dark” since again, no one can see what your backend looks like. Thats why I suggested installing the theme on a separate server to show that the theme isn’t the issue, its an error somewhere in your code…..
I was the only one taking the time to give you suggestions while trying to help you, but if you don’t want or need my help then I’ll just let someone else help you from now on 🙂
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
Eric, are you hired by AppFinite? If you’re not and you like the rest of us, just here to help as we can, then please accept my apologies.
If you read what I have written, you can see that I have followed your suggestions, at least as best as I can understand. I have reported on the results as well.
No I’m not hired by Appfinite or anyone (freelancer). It probably looks that way since I answer so many questions here and on the StudioPress forums. So no worries.
I create awesome sites for awesome people! Contact me if interested – ericsanchez1585@gmail.com
- You must be logged in to reply to this topic.