Sorry for the inconvenience. From the screen shot it looks like it may be a JavaScript error.
Need a little more info. Browser and version would be good. If you can create a temp admin account and email me the details that would also drastically decrease the time it will take me to solve the problem.
danieliser @ wizardinternetsolutions.com
It happens on all browsers I’ve tried: firefox 24.0 and chrome 30.
Can you please give me more details on what to try to fix it before creating a temp admin?
Thanks
Use the browsers console to see if there are any JS errors when the page is loading. I haven’t seen anything else cause issues like you are describing.
It is most likely a conflict with another plugin or theme causing the issue which is why I asked for temp access. If you can find the bug I can fix it.
This is the error that appears:
var td = document.getElementById('titlediv');
var qtd = document.createElement('div');
var h = document.createElement('h3');
var l = document.createTextNode('Title (English)');
var tw = document.createElement('div');
var ti = document.createElement('input');
var slug = document.getElementById('edit-slug-box');
ti.type = 'text';
ti.id = 'qtrans_title_en';
ti.tabIndex = '1';
ti.value = qtrans_use('en', document.getElementById('title').value);
ti.onchange = qtrans_integrate_title;
ti.className = 'qtrans_title_input';
h.className = 'qtrans_title';
tw.className = 'qtrans_title_wrap';
qtd.className = 'postarea';
h.appendChild(l);
tw.appendChild(ti);
qtd.appendChild(h);
qtd.appendChild(tw);if(slug) qtd.appendChild(slug);
td.parentNode.insertBefore(qtd,td);
it is on this line:
td.parentNode.insertBefore(qtd,td);
It looks like it has a conflict with to do with qtranslate. If qtranslate is deactivated it works. Otherwise no.
Forgot to add the error:
TypeError: td is null
td.parentNode.insertBefore(qtd,td);
I will grab a copy of qtranslate and try to debug that.
Thanks. If I can help with more info please let me know.
This has been marked for the next small release as long as its not a major fix. If it is it will go to the next minor release of v1.3.1 which should be nearer the end of the month.
1’m using easy modal 1.3.0.2 and I noticed that the first modal would briefly flash on and off as I moved between pages regardless of whether I was on the page where the button is placed.
I thought this was because I had set it to ‘Setewide’ “Yes”, so I switched it to “No”. Now the button does not work, where as it did before.
Please advise me. The button is: <button class=”eModal-2″><span style=”color: #330066;”>More…</span></button>
You can see all the buttons here: http://communication.org.au/governors-fellows/
@davivsless you should start a new thread since its an unrelated issue. But if you only need the modals on one page now with v1.3+ you can do it inline in the page editor with shortcodes or via the Easy Modal settings section below the editor. You can select any modal that is not sitewide to be loaded on that page.
As for the flash this is the first report of it so i will need to see what is happening when you get the modals loading again.
Hi,
The problem still appears. I have the latest version 1.3.0.3.
When do you think that it will be fixed?
Kind regards,
Hey JustMe2007,
I looked into it and submitted a request for an update to qTranslate. The problem seems to be that they load their scripts and css on all pages to allow you to translate nearly anything. But in their JS they do no checks for whether or not an element exists before attemtpting to modify it.
Basically whats happening is they get the titlediv on every page. But if that div doesn’t exist it still tries to modify it resulting in an error that stops other JS from executing.
