Old versions of PRO

Support
#1

Hi guys,

i was wondering if it was possible to know where and if you keep an old version of PRO (2.1.6) ?
i’m having a few issue on a staging server and i wanted to rule out a theme issue (i was using 2.2.0 beta2 and even when i update it to the official release of 2.2.0, it still says beta2 in the pro validator page.)

the error is the following:

Notice: Undefined index: action in /xxx/xxx/domain.com/public/wp-loader.php on line 67
Notice: Undefined index: auth in /xxx/xxx/forge/domain.com/public/wp-loader.php on line 104

i searched online and it seemed like a plugin issue but i disabled them all and the problem persisted.

EDIT: i can confirm that the issue was the RC2! downgraded to 2.1.6 and everything got fixed.

#2

Hi @elpanda13,

Thanks for reporting this :slight_smile:

Yes, please use the stable version, for now, the beta is released for testing purposes and may still contain some issues. Though, you should see a 2.2.0 after the update instead of the beta. How did you do the update? Have you tried deleting the entire beta theme folder? Maybe the update isn’t complete and you still see some of the files from the beta version.

Thanks!

#3

i renamed the entire folder and made a new one, so all the files were the correct ones.

#4

Hello There,

We are just glad that you have figured it out a way to correct the said issue.
Thanks for letting us know!

Best Regards.

#5

Ok i have really no idea what on earth is going on, i tried to update another site and the SAME exact problem re-presented. i have no idea where on earth is this coming from :/. it’s not browser or any other type of cache, the server doesn’t have any kind of caching enabled nor does the site, yet everytime i try to update that happens. this time i updated from 2.1.6 to 2.2.4, the entire site’s directory says everything’s alright, everything’s 2.2.4 but the site says it’s 2.1.6, if i try to edit anything the entire framework starts throwing errors (cs-vendor.js related).

i thought it was the release candidate, but it wasn’t really it. is there something in a server that could be causing this? as i said earlier, this server doesn’t have any kind of caching enabled. it’s a VPS running nginx from Digital Ocean.

#6

Hi there,

I can confirm the versions are still old, but I couldn’t fully check it since the login has no admin capability. Would it be okay if you grant us an admin access?

Thanks!

#7

Done, admin capability granted.

#8

Hello There,

I have logged in to your staging site. I exported your Theme Options settings in Pro > Validation for backup. And then I went to Appearrance > Themes and deleted Pro Theme. This is to make sure that there is no corrupted file whatsoever. I have re uploaded the Pro Theme fresh from my dashboard which is version 2.2.6. When I went back to Pro > Validation, it is still displaying Pro 2.1.6 which is weird. I even deactivated the plugins and still the same. There could be something in your WP installation that is causing this. Could you please provide us FTP details to your staging site? We need to investigate the files which could be behind all this issue.

Thank you in advance.

#9

Credentials given in the secure note above.

#10

Hi,

The sftp login provided doesn’t seem to work.
Kindly check again and let us know.

Thanks

#11

Hey Alejandro,

Sorry for the confusion. The credentials work. I’m still currently checking.

#12

Hey Alejandro,

I have investigated and the only thing I noticed in the file system is my wp-config.php changes. I’ve changed the salt keys and also commented out the “disallow file edit” config but they don’t take effect. Changing the salt keys should log me out but I remained logged in. The file edit config also has no effect.

The theme version is correct in the file system. It seems like your site is getting data from 2 sources.

There’s a cache folder in your server but I’m afraid to touch it. Try contacting Digital Ocean if they can think of a possible cause for this. I could not replicate this in my local test site (nginx)

Can you also give us database access?

Thanks.

#13

Ok, sure, i’ll leave you datbase access in private. about the cache folder, i don’t really think they would make any difference, the files in there haven’t been updated in like 1-2 years.

EDIT: Files already uploaded as a secure note.

#14

FOUND THE ISSUE!

my server has FORGE installed and turns out it had OPCACHE enabled! it must’ve re-enabled itself after an update because i had previously deactivated it!

#15

Hi @elpanda13,

Glad it’s okay now, was still searching but yes, really due to cache.

Thanks for sharing :wink:

#16

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.