Welcome to the Question2Answer Q&A. There's also a demo if you just want to try it out.

How to reposition/override the edit and hide buttons on question view page ?

+3 votes
asked May 2 in Q2A Core by UI-UX-DESIGNER

i want to reposition only the edit and hide buttons on question view page. How can i override them as their code isn't in qa-theme-base.php file ? I know that the code is in the question-view.php file:

if ($question['hideable'])
                    'tags' => 'name="q_dohide"'.$clicksuffix,
                    'label' => qa_lang_html('question/hide_button'),
                    'popup' => qa_lang_html('question/hide_q_popup'),

Is there a way to add this code in my advance theme qa-theme file ??


Q2A version: 1.7.4
commented May 3 by UI-UX-DESIGNER
Not exactly what i want @sama55. Let me explain better...Right Now the question page buttons are merged together (Answer, Comment, Hide, Lock, Edit etc).
I know how to call them inside the qa-theme.php and reposition them to the place i want. What i cant figure out is how to call/overide part of them. eg lets say i want to reposition only the edit button and leave the rest of them as they are. How can i call/override the edit question button only and apply my style to it ????

1 Answer

+1 vote
answered May 5 by pupi1985
selected May 7 by UI-UX-DESIGNER
Best answer

It is a bit unclear what you're trying to do. However, there are only 3 possible solutions to whatever the issue is: one is fully frontend, the other one will require backend and the last one a bit of both.

In short, if you can do whatever you want to do using CSS go ahead. You just need to apply the CSS to the appropriate button class. I took this screenshot from this same question:

As you can see, each button has their own CSS class that allows to uniquely target the element. You could even use some jQuery to play with the DOM, just make sure the form is always submitted.

The backend solution involves modifying the $qa_content array. If you need that, most likely you will be changing the HTML structure of the page before it is actually sent to the client. This might result in issues with plugins that expect the original HTML structure (or content in the array). This is probably a harder approach as you will have to reposition the element and creating a container form that would allow the button submission using PHP.

You could also make a mix of the approaches and add a new button wherever you want, hide (display: none) the original one and make sure the new one sends a click() event to the hidden one. This one might should be the simplest approach as you don't have to worry about the form submission.