Forum Replies Created

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Also, I just tried changing my PHP version with Bluehost, first to 5.4, then 5.6, nothing changed. I’m not totally sure I did that right though.

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    It IS indeed working now. One other question – can non-wordpress users use the forum? I tried to log in from another browser and it just wanted me to log in with wordpress account, I couldn’t just use an e-mail address…

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    I think that code did the trick!
    Yes the 5.3 was activated and the way the error came up changed.

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    I clicked the back-browser and got back to the admin but anything I click leads to that error code. Like if I click “posts” it goes to that.

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Oh no, I’m now locked out of my site all together.
    I updated PHP to 5.3
    I was able to activate the plugin. I didn’t see Forum appear on the menu on the left so I clicked “Dashboard” and now I have this, but on an entire blank page:

    Parse error: syntax error, unexpected T_FUNCTION in /home/content/28/5685028/html/veganingredientcheck/wp-content/plugins/asgaros-forum/includes/forum-widgets.php on line 104

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Oops, I didn’t see your code fix above and already initiated the switch to 5.3, sorry about that! I should know in the next hour if that worked.

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Hello.

    WordPress 4.4.2
    PHP 5.2

    I see I have the option to use 5.3 or 5.4 on godaddy
    Which should I choose if 5.2 is the problem?

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Thank you very much, it worked!!
    I did it with id’s.

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Btw, I mistyped 3177 in the message above – it should be 3117 and I did put the correct number in the CSS.

    I think the dropdown menu pages are inheriting this new style of the arrow cursor. Am I inspecting the element wrong?

    Thread Starter rebeccaschiffman

    (@rebeccaschiffman)

    Hi Laura,
    Thank you so much for the response! I’ve learned a lot from that it I did not know before – including inspect element! I was able to create the new menu with the custom link as the button and the # works so that it doesn’t go anywhere.

    Now I’m trying to follow your instructions to make the cursor be an arrow while just on PHOTOS but I’m having trouble. So far, the arrow shows up while hovering on the nav button but there’s also an arrow for all of the pages on the drop down menu below – those should have the hand because they are clickable links.

    Inspect element revealed for the PHOTOS nav button:
    <li id=“menu-item-3117” class=“menu-item menu-item-type-custom menu-item-object-custom menu-item-has-children menu-item-3177”>

    So far each of the following lines of code, tried separately, result in all the links in the PHOTOS dropdown menu having an arrow for the cursor.

    .menu-item-has-children a{cursor: default;}
    #menu-item-3117 a{cursor: default;}

    Do you know how I can apply it to only the nav button? I’m confused as to why it would apply the arrow to the dropdown pages because they don’t have the same id or class as the ones I’m using here for the nav button. I left #menu-item-3117 a{cursor: default;} in the CSS so for now the PHOTOS dropdown menu has the arrow.

    Thanks again!

Viewing 10 replies - 1 through 10 (of 10 total)