[kelwinrack]

Cryout Creations leverages the native WordPress Customizer API to power its advanced, real-time theme control panels. Their proprietary framework is lightweight, extensible, and deeply integrated into WordPress, allowing users to adjust layouts, typography, colors, and more—without touching code. This foundation ensures full compatibility with core updates and promotes a user-friendly interface across all themes. By combining built-in WordPress standards with custom enhancements, Cryout delivers a flexible, future-proof customization experience tailored for both beginners and developers.

[picnic_23]

I ran into something similar using the Bravada theme. I found that the list elements (ul, ol, li) are getting a padding of 0 in the css file, hiding the bullets/numbers outside of the text area.

Try adding this to your css file or Customize > Custom CSS, and see if it helps:

ul, ol {
padding-left: 35px;
}

[magnus]

Regarding this XSS vulnerability that has been a problem for a long time ….

I thought it might be better to change theme so I have searched and tested a lot of different themes. But I have not found any other theme that has a plugin that is as good as Serious Theme Settings, not even in the paid PRO versions. I have tried OceanWP Pro and Astra Pro, but they are not even close to what Serious Theme Settings can do.

All of us have probably been using Serious Theme Settings for so long that we do not appreciate what it can do and just take it for granted.

The Serious Theme Settings plugin is actually so good that it should not be free, but rather it should cost money.

So if the problem with fixing the XSS vulnerability is the economy, then I and probably many other users are willing to pay for the Serious Theme Settings plugin.

With that said, I wish everyone a happy new year.

• This topic was modified 7 months ago by magnus.

[scldad]

OK. Just found the earlier posts.
Nil desperandum.

[LCGoldman]

I haven’t found a solution yet.

Website: www.talkinghorseracing.com

[bedard5115]

Jetpack just returned a security warning tonight on Mantra 3.3.2.

These items require your immediate attention
The theme mantra (version 3.3.2) has a publicly known vulnerability.1h ago
Fix threat
Vulnerability found in theme

[xofmedia]

I’m not sure how old this problem is but I filed a couple support tickets and haven’t heard back. I’m running Fluida Plus now but this problem is also on Septera Plus for other sites I use the themes for.

I found this previous post:
https://www.cryoutcreations.eu/forums/t/comment-counter-on-blog-page

This seems to confirm Cryout Creations are aware of the issue in August 2023, but it’s now 2024 and no fix… Is support dropping?

I used this fix by just adding some css (style.css):

/* Removes itemprop=”discussionURL” */
.comments-link {
visibility: hidden;
}

This seems to remove the problem areas for me while leaving the comments themselves on and the comments count in place for thumbnails (ie: related posts). Temporary fix I’m hoping.

Website: xofmedia.com

[drwolfsherz]

Additional Informations can be found here:
https://patchstack.com/database/vulnerability/cryout-serious-slider/wordpress-serious-slider-plugin-1-2-4-cross-site-request-forgery-csrf-vulnerability?_a_id=110

[ryanjenson90]

Hi everyone, I’ve encountered similar issues with emojis not rendering correctly in animations. One workaround I’ve found is to use HTML entities for the emojis instead of the actual emoji characters. For example, you can replace the heart emoji with ❤ in your title. It’s not a perfect solution, but it might help as a temporary fix until the bug in the animation tool is resolved. Hope this helps!

[mr108]

I found the solution in another post.
#access { margin-top: 0px; }

Increasing the number from 0px to more will create that space/gap

[bassicsax]

Yes, like you, I have not found any other themes I am happy with. Like you, I have been their customer for years. My subscription is due at the end of this year. I am dreading that. I am still wanting to support them, but quite honestly, I don’t see how I can. I feel like I have been let loose in the middle of the ocean with a life jacket and am trying to make my way to shore. It is indeed overwhelming.

Fingers crossed for both of us Steve!…

[MikeEckman]

Carrie, I found a workaround to make that text go away.

Go into Appearance, Customize, then when in the Customizer, go to Post Information, Meta Information, and uncheck the box for Display Comments.

Disabling that option will make the itemprop=”discussionURL” text go away, but it also takes away the count of how many comments are on each post. If you can live with losing that number, you can get rid of the text that is showing up now.

Hopefully someone fixes this as this is almost certainly only the beginning of more defects that will show up as WordPress is updated, but these themes are not.

[rarogames]

found it
personalisation/general/content images

[Wendy]

I found how to change the site title in the Tempera settings, but ITC Willow is not in the fonts. How do I add it?

[Netviator]

Apparently I was able to resolve the issue:
I created a “home” page where I placed the welcome text, then changed the choices in the general options by deciding to choose that page as the static page upon arrival on the site and not the “articles page”, then in Septera’s customization I set it as “disabled” in the “Setting” section of the “Landing page” and, after saving everything, as if by a miracle I found the home page and no longer the blog articles.

I hope I was helpful to someone.

Have a nice day everyone

[tdokta]

found the place now and have replaced code with: none
thanks

[reamen]

Oh sorry. i was too early with my question. have now found the solution myself.

If someone else has the same goal.
The code:
.post-thumbnail-container .featured-image-overlay::before {
opacity: 0;
}

I have entered in the ccs editor

[3cstudio]

Since a number of threads haven’t been responded-to for weeks, I did some digging on my own — this is what I found that might be the solution: Add this to the Custom CSS in the Customizer:

/* Hide element on Desktop */
@media only screen and (min-width: 981px) {
.hamburger {
display: none !important;
}
}

I’m checking with the client to see if their Windows viewers can now see the menu on a single line.

[LauraE]

I finally found the code that put the border box around the links in the main menu. I was able to alter that code in the Additional Css.

If anyone else wants to get rid of that border box that lights up when you hover over it: This is the code that is causing it:

#access > div > ul > li > a > span::before {
I changed the border value to:
border: none !important;

Laura

[philsego]

I found it. There was a conflict with “W3 Total Cache”
I disabled it and the site is now working properly.

[TigerWolf]

Did you found out what plugin made it happen?

[TigerWolf]

unfortunately i haven’t found a solution for this 🙁

[earlmacdon]

I am curious if you found a resolution to this issue, TigerWolf.

My site is running on PHP v7.4. I tried to upgrade the version of PHP to v8.1 as my host requested, but when I do so, the site doesn’t work. Similarly, v.8.0 doesn’t work. My host is no longer supporting outdated PHP versions, so I am concerned. I love my current Nirvana template and would hate to switch.

Website: www.earlmacdonald.com

[Zed]

The not found / search form is displayed on the homepage of any WordPress site when it has no content (posts) to display. This can be avoided by publishing posts or setting the homepage to display a (static) page instead.

---

If you like our creations, help us share by rating them on WordPress.org.
Please check the available documentation and search the forums before starting a topic.

[lorenz]

good morning

I have found out.
The search box was gone when I placed another widget there.

[michelle]

Thank you….I finally found the page titles. I had actually originally set it to Page/Category Titles “Always Hidden”, and it wasn’t working, which I think is why I was so confused. I switched it to “Hide on Pages” and that did the trick…I thought Always Hidden should have done it too though?

As for the screenshots, I’d love to see what the home page looks like on your device, or the Learn More page….the games page is pretty different from the rest of the site, but even then it seems like the formatting is better on your device as parts of the games were cut off one mine.

I changed the menu, and the hamburger is now showing up, but then the in-line menu clashes with/over my logo header so I have to keep that off now, which isn’t ideal.

I think the issue with the home page is that I have the Landing Page enabled and that’s what isn’t working in mobile? Is the landing page header just not compatible with mobile, or do I need to reformat it somehow?

Can I post a screenshot here somehow to show what I’m seeing on my landing/home page? (the overly large text and the landing page header that’s also not being correctly resized)

[alannah]

Hi folks,

Had the same problem with the buttons in Serious Slider since the WordPress 6.1 update. I found a workaround that works for me.

Find the code for whatever button or buttons you wish to hide and code display:none in the customizer under Additional CSS. In my case working in Fluida it was:
.seriousslider-theme .seriousslider-caption-buttons a:nth-child(2n), a.staticslider-button:nth-child(2n) {
display: none
}

This hid the button I couldn’t change or delete. Then I created a new button in the Slide where you can create your own buttons, labels etc. to take it’s place for the time being. You can find help in coding buttons in the W3 Schools website.

Hope this helps people until Cryout can find a fix for the incompatibility that WordPress 6.1 created!

Cheers

• This reply was modified 2 years ago by alannah. Reason: Included unintentional likn

[Heartlight]

Hi you can close this topic – I found it. I was in the ‘colors’ section but I had the wrong hex code and so it was being white instead of my color.

[gmaravel]

Ok, I searched in the Stylesheet and found it at .lp-box-title …

[deKay]

I’ve just noticed I get a similar error. If I search my site, and a blog post without a Featured Image is found, this error comes up:

Warning: Trying to access array offset on value of type null in /[path-to-wp-removed]/wp-content/themes/kahuna/includes/loop.php on line 295

I’ve found that the server is running PHP 8.1, and if I change it to 7.4 then the error goes away.

I think this is because in PHP 7 if you try to get the contents of an empty (or non-existent, perhaps) array you get a response of “null”, whereas in PHP 8 you get *nothing*, and so an error. Willing to bet your errors are for the same reason, and if you can change your server to PHP 7.4 it’ll fix it for now until Kahuna gets updated to work with PHP 8+ fully.