calendar button problem

  • Resolved Ali R?za Türkmen

    (@farkindalikarasi)


    1 month, 3 weeks ago

    I have a little problem. I search it on forum and tried to solve with chatgpt but i didn’t solve it. I have a problem with calendar buttons like ”next day, next week”. I think there is a conflict with my main theme colors. I can’t see buttons. I can use them but can’t see. I tried to fix it with custom css but it didn’t work. can you help me about css codes please? thank you.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Ali R?za Türkmen

    (@farkindalikarasi)

    Hello,

    I am encountering a problem when I run my page. I searched the theme codes and found the error: “Could not load content for https://farkindalikarasi.com/wp-content/plugins/eventprime-event-calendar-management/public/moment.js (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE).”

    Additionally, the moment.js file appears to be empty.

    Could this be the source of my problem?

    Plugin Support EventPrime Support

    (@eventprimesupport)

    Thanks for reaching out to us.

    We have checked your issue, and it seems that the accent color for your theme is set to white. Our plugin, EventPrime, inherits the accent color from the theme to ensure that design elements match. Since the accent color is white, it’s causing the buttons to be invisible.
    We will address this globally in our upcoming release. Meanwhile, you can apply the following CSS to resolve the issue:
    Add the following CSS to your theme’s style file, or
    Go to EventPrime settings from the dashboard’s left menu, click on the “Custom CSS” tab, and insert the code below:

    :root {
    --themeColor: 6, 147, 227;
}

    This should make the buttons visible again. As for your other queries, our team is currently reviewing them and will provide an update shortly.

    Thread Starter Ali R?za Türkmen

    (@farkindalikarasi)

    thank you. at first it didn’t solve my problem. i think because it prioritizes the properties of the theme. but adding the ‘!important’ command at the end solved it.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.