Forum Replies Created
Looks to be working great. Thanks!
These changes worked well as far as I can tell. However the recent posts widget in the footer still links the author. Can you make it such that the widget respects that setting (or guide how to override that on my side)?
Thanks!
I’m still awaiting guidance on this. Any updates?
I installed the theme and deselected the Post Author option. This made the entire author go away. But as I stated originally, I want to show and credit the name of the author, but I don’t want to link to an author’s page. It’s not a page that we manage content for or one that we want search engines/people navigating to.
With project categories, I want to remove them altogether. Hiding them in CSS still leaves the links in the actual HTML, causing people and engines to find their way to those pages. We don’t want that.
So to summarize:
- Blog Author – Leave the text, but get rid of the hyperlink
- Project Category – Remove entirely from page
I don’t see those options under Theme Settings > Blog. (See attachment.)
Also, that wouldn’t address the project categories.
Please advise.
Thanks.
For clarity, you mean that following the upgrade to Redux, the existing pages which are Unyson will remain Unyson. I’ll have to continue to keep the Unyson plugin in place to maintain those pages. And for new pages I should be using WPBakery instead (using Frontend editor which gives me access to the layout and content elements). Do I understand that correctly?
Is there a way to convert pages from Unyson to WPBakery, or would I need to redo each page manually?
Thanks, I had come across another post with similar suggestion. I tried that on Friday and that didn’t resolve the issue. However, this morning, things appear to be working correctly, so perhaps something was cached somewhere. In any case, the situation appears to be resolved.
Is there anything I should expect will break in upgrading to Redux (e.g., mega menu, portfolio, pages, other plugins)?
Does Redux just provide a different page design UI/UX? Not sure what overhead I should expect to incur by making the switch.
How do I go about switching over to the WPBaker page builder? I provided an attachment of what I see when I come to a page.
Can existing pages be switched over?
This works and I guess is a fine interim solution, if a little odd to use a text component strictly to render an image.
One point of note, with this approach I lose access to the alternative alignment option on mobile. For instance, it would make sense to have this left-aligned on web and center-aligned on mobile.
Is there a strong reason not to introduce width and width(mobile) attributes that would scale the source image accordingly for ultimate design flexibility?
The only option I have in that dropdown other than “Full” is “Large”. That doesn’t really give me design control, especially since I don’t know what the impact of it is on the site without trial and error. And in this case, setting it to “Large” presents the same as “Full” (i.e. it takes up the full column width).
Images like these would be used throughout the site. It should be uploaded to media once, and then should be reusable on different pages in whatever size/presentation makes sense for the page. For that to happen, having a text field where I could specify image width as px or % would be appropriate. As it is currently, I have to upload multiple copies of the same image at different sizes.
See private.
I’m using the Unyson image element, sitting inside a half-width (if I recall correctly) column, with header and text elements, inside a section.
It’s the AWS partner logo. The one there currently was sized specifically for the current space. When I replace it with a bigger image, the image takes up the full width of the column, which is undesirable.
UPDATE:
I have found an Image Settings section down near the bottom, with the toggle I was looking for to disable the featured image.
Clearing the cache did not help. However, excluding the following file from JS minification appears to resolve it.
wp-content/plugins/unyson/framework/extensions/forms/includes/option-types/form-builder/items/recaptcha/static/js/frontend-recaptcha.js
I had to restore some of these in the interim. Please let me know a window you’d like to review, if necessary, and I can try to accommodate again.
I just deactivated all plugins except those two and I’m still seeing the issue. Please confirm.
OK, I’ve gone ahead and done that.
Confirmed, this appears to have been resolved. Thanks!
The fix provided appears to resolve the main original issue. But I did observe a follow-up issue in the provided Beta. When I click on a menu item, I’m seeing the attached JS error in the console. It doesn’t appear to be causing a material issue, though.
Seems to be an issue in /wp-content/themes/jevelin/js/scripts.js. There are 2 instances of “a[href*=#]” that seemed to be causing the problem. I put quotes around the # and that seems to have resolved the issue.
I can’t say for sure whether that caused other collateral damage elsewhere. Also, I’m concerned my changes will be overwritten next time I update my theme. Please advise.
