Bob_R
Active member
It could, yes.
Running this query should confirm it:
Code:SELECT * FROM xf_permission_entry WHERE user_id =x;
Here's what I got.
Don't know what it means or if correct or if needs fixing.
Please advise. Thanks.
It could, yes.
Running this query should confirm it:
Code:SELECT * FROM xf_permission_entry WHERE user_id =x;
Yes, I think that that is it. It will only suggest tags where a word begins with xperia. Underscores aren't considered "word-breaking" characters to programmers. You may wish to change the tag from "Sony_Xperia_Z1" to "Sony Xperia Z1". That's how I do it.Thanks for your reply. It does not work for my example. Can it be due to underscores ?
=> Would Sony_Xperia_Z1 be proposed for "xperia"?
It is great for SEO.does this do anything for seo?
OverlayLoader for posts/18/edit-inline
xenforo.js?_v=eeb83a36:564 ExtLoader Failure parsererror 200
xenforo.js?_v=eeb83a36:537 Loaded css 0, editor_ui
xenforo.js?_v=eeb83a36:537 Loaded css 1, bbm_editor_redactor_autocss
Open a conversation with him: @Dinh Thanh the support is excellent.I'd like to pay to support the developer, and remove the branding, but I can't figure out where to go to do that. Can someone point me in the right direction? Sorry if it's plainly obvious and I'm being stupid!
I'm getting a strange console error with this mod installed.
If I click "edit" on a post then nothing happens but the console shows this error....
If I click edit for the second time then it works. any ideas? @Dinh Thanh
If I disable this mod then everything works fine.
Just to pin this down a little more @Dinh Thanh ..... it only happens in forums that a closed to new posts / replies.
Did you check your censored list? If there is any, please removed it.Did you have a look on this, please @Dinh Thanh?
https://xenforo.com/community/threads/tinhte-xentag.32231/page-67#post-879588
Importing from vB hardly stopped and there is no chance to know why. Happened in 2.1.3 The same import, without changing anything with 2.1.0 went through without error. So there must be a check or error in 2.1.3 which was not in 2.1.0
We use essential cookies to make this site work, and optional cookies to enhance your experience.