occban
Forum Replies Created
-
Forum: Themes and Templates
In reply to: [Portfolio Press] Fatal error after updating theme to ver 2.7.2I had the same problem. This function call is on the Full-width Portfolio Page Template (templates/full-width-portfolio.php). I didn’t find it in any of the other template files.
Change “portfolioplus” to “portfoliopress”. That solved it for me.
Forum: Plugins
In reply to: [SlickNav Mobile Menu] Settings won't saveMuch appreciated! Will keep it in mind if I run into this problem again.
Forum: Plugins
In reply to: [SlickNav Mobile Menu] Settings won't saveUnfortunately, I had to use a different solution for this project. Technically, this issue is “resolved”.
Forum: Plugins
In reply to: [SlickNav Mobile Menu] Settings won't saveThanks for your quick response. I just did a SQL dump from the dev site and imported it into the live site (phpMyAdmin interface on both ends). I did have to set the file to be compatible with MySQL40 because I ran into with the live site rejecting the “utf8mb4_unicode_ci” character set. Then I used searchreplacedb2 (InterconnectIT.com) to replace the dev URL with the live URL. Done this countless times before without incident–including sites with this plugin. The only difference this time was the compatibility issue on the receiving end.
Weirder still is that the options technically DO save to the database; I see them in the _options table. The plugin just doesn’t seem to see them, and thus doesn’t work.
Thanks, Nick M. I just downgraded to 4.3.5. I will wait for the developer to address the problem.
Same problem. While I can upload images directly to the Media Gallery, I can’t upload-and-insert-into-post. Also, when I try to insert an existing image into a post, there’s no image info (title, alignment, size, etc.).
For what it’s worth, when attempting to insert an existing image into a post, Firebug shows the following error:
ReferenceError: gllr_notice_wiev is not defined
FWIW, I had the same problem but discovered the cause:
The wp_nav_menu() function will accept a custom value for the menu_id parameter (which is then applied to the UL); the default value is ‘#menu-{menu slug}’, which is what SlickNav now looks for. So if menu_id is set to anything other than the default, then SlickNav won’t find the UL.
In order to get SlickNav 1.5.6 to work on my site, I had to remove ‘menu_id’ => {custom value} from my wp_nav_menu() args array.
Thanks for your reply. Setting permalinks to Post Name had no effect.
The all-user listing is here: https://www.acaac.org/acaac-registry/. There is one user listed, as there should be. Clicking on the “More” link (https://www.acaac.org/acaac-registry/user/5) still produces the 404 error.