Martok
Well-known member
I'd say you didn't upgrade it correctly if you have 2 copies of the parent style.Hello?
I'd say you didn't upgrade it correctly if you have 2 copies of the parent style.Hello?
I'd say you didn't upgrade it correctly if you have 2 copies of the parent style.
Have you not renewed your license maybe? All updates are showing for me:Yes, I realize that. I downloaded the add-on (1.7) from the Audentio site. Uploaded to my server. Upgraded the add-on. There was nothing in my AdminCP (Appearance > UI.X > Styles) because per the directions I disabled the add-on. Once enabled I didn't see a Upgrade option (step 5) it was an Install option. So I installed automatically.
I wanted to install manually but on the Audentio site the changelog for the style was from August.
The instructions don't seem to jive with what has to be done. I wish they were more precise and exact. I'm starting to regret purchasing this
Upgrading instructions:
- First, and foremost, make a backup of your theme. A backup of your site as a whole is never a bad idea either especially if you are going to production board
- Second, disable the UI.X Add-on. This will cause some PHP errors if you are missing tables, so its best to just disable it. If you do accidentally forget, you must add $config['enableListeners'] = 0; to your library/config.php file, then start back at step 2.
- Download the latest version of the add-on, located in your downloads area as a green button
- Upload the contents of the /upload/ folder within that extracted zip folder to your root XenForo directory
- After that has finished, go into your XenForo ACP and click on the UI.X add-on. You will get a modal that says upgrade add-on. Browse for the .xml of the add-on that was in the .zip file and continue
- After that has finished, you can choose if you want to update the theme via the add-on or manually. We recommend doing it automatically so that is how we will continue in step 7.
- If you go to Appearance, on the sidebar you'll see UI.X > Styles. Click Update next to the style you want to update, or you can install fresh here as well
Have you not renewed your license maybe? All updates are showing for me:
View attachment 123637
Also, are you on XenForo 1.5.3?
Your problem is that you have carried out an install rather than an upgrade.
This is the UI.X thread and add-on here. Rekt is here:- I just bought REKT on Saturday. My license is valid.
- Yes, I am on XenForo 1.5.3
This is the UI.X thread and add-on here. Rekt is here:
https://xenforo.com/community/resources/rekt-with-custom-homepage.4197/
As you will see, Rekt is still on version 1.5.0.1. Therefore there currently is no update. You need to remove the duplicate parent and child styles that you installed.
BTW you can click on the post number (in this case #5830) to get a URL to copy and paste in a post, it saves others having to look through to find the post. Like this:What does post #5830 in this thread mean then, if I'm up to date?
BTW you can click on the post number (in this case #5830) to get a URL to copy and paste in a post, it saves others having to look through to find the post. Like this:
https://xenforo.com/community/threads/ui-x-paid.57944/page-292#post-1014518
It means the UI.X add-on has been updated, not the style. The add-on provides some of the functionality for the UI.X based styles (which includes Rekt) including the automatic update for a style.
Your style, Rekt, hasn't had an update since August. That's why there is no automatic update option.
If you watch the Rekt thread that I linked you to, that will tell you when there is a style update. You should also receive an email from Audentio when the Rekt style is updated.
You update in the same way as any other add-on. If you have 1.0.7 installed already then you already have the latest version.OK, thanks.
So, how do I ensure that I've updated the UI.X add-on correctly. The one I've downloaded is 1.0.7 same number as latest version.
You update in the same way as any other add-on. If you have 1.0.7 installed already then you already have the latest version.
I'm using a (more or less) untouched UI.X on a (more or less) untouched XenForo, just for fun (that's why there are not really many things going on there...). However, I recently noticed that Firefox (by default) does not show me the login pop-up, it only shows the loading bar and spits out some JavaScript error:
Code:ReferenceError: gapi is not defined xenforo.js:215:1
Disabling Firefox's built-in "tracking protection" solves the issue. As Firefox is commonly used, I wish there was a way to fix that right in the code though.
Any ideas?
(xpost from here)
plusoneButtonInit: function(el)
{
if ($(el).find('div.g-plusone, .GoogleLogin').length)
{
var locale = $('html').attr('lang');
var callback = function()
{
if (typeof(gapi) !== 'undefined') {
$(el).find('.GoogleLogin').each(function() {
var $button = $(this),
clientId = $button.data('client-id');
gapi.signin.render(this, {
callback: function(result) {
if (result.status.method == 'AUTO')
{
// this is an auto triggered login which is doesn't really fit
// and can cause some bad behavior, so disable it
return;
}
if (result.code)
{
window.location = XenForo.canonicalizeUrl(
$button.data('redirect-url').replace('__CODE__', result.code)
);
}
},
clientid: clientId,
cookiepolicy: 'single_host_origin',
accesstype: 'offline',
immediate: false,
requestvisibleactions: 'http://schemas.google.com/AddActivity',
scope: 'https://www.googleapis.com/auth/plus.login email'
});
});
}
};
if (window.___gcfg)
{
callback();
}
else
{
window.___gcfg = {
lang: locale,
isSignedOut: true // this is to stop the "welcome back" prompt as it doesn't fit with our flow
};
XenForo.loadJs('https://plus.google.com/js/client:plusone.js', callback);
}
}
},
Ya it is tracking, but for a somewhat sensible reason (imo). I've submitted it as a bug report to XenForo https://xenforo.com/community/threa...-to-prevent-bug-with-content-blockers.109512/ to hopefully have it rolled into an official release.Technically it is tracking users...
Hmm, patching core files. Always a great idea. It seems to have worked though, thanks.
We use essential cookies to make this site work, and optional cookies to enhance your experience.