Hi,
I have issues with dev sites using multiple subdomains like staging1.domain.com etc.
My previous issues reported earlier might be related:
https://toolset.com/forums/topic/issues-with-multiple-staging-subdomain-license-key-activation/
and
https://toolset.com/forums/topic/at-relationshipws-page-and-clicking-add-new-nothing-happens/
Today I contacted Siteground, my hosting provider, reported them your suggestion from here:
https://toolset.com/forums/topic/at-relationshipws-page-and-clicking-add-new-nothing-happens/#post-1399149
but they responded they can not do that, this is intentional from their side.
I copy here their response:
"This is intended behaviour and how our Staging tool is made to work and not a bug.
The Staging tool uses mod_host, mod_substitute mod_headers Apache modules in order to have the current setup working correctly and your Staging website is made to work this way and their SITE and HOME URLs need to be that of the Live website in order for the Staging tool to work properly with them and to avoid any issues with the Staging push once it is done.
With this in mind, please revert the changes which you have done to the Staging website as this will create issues on the Staging website itself and it will also cause issues on your Live website once this Staging website is pushed."
So what can we do?
Thank you!
Hello,
To avoid those compatibility issues, I suggest you try to follow our document to migrate your live production website to develop domain name:
https://toolset.com/faq/how-do-i-migrate-a-wordpress-site-from-one-domain-to-the-other/
For example, use third party plugin:
Duplicator – this plugin helps you to migrate your entire site, including the files and the database
Hi,
it is nothing about site migration, I have no problem with it in general...
a) I'm working with staging sites with Toolset (and WPML) for years (at the same hosting company Siteground) and it was not an issue earlier, so something has changed recently (weeks or months ago?) in Toolset (and WPML) licensing process or elsewhere, which causes these issues.
b) I linked 2 issues in my original post and I suppose they might be different indications of the same reason.
I add a 3rd thread for the same reason:
https://toolset.com/forums/topic/settings-change-for-a-post-field-field-group-is-not-changed
c) If you check my Toolset Dashboard / Sites at
https://toolset.com/account/sites/
you can see warning signs in Types column, showing I should update those plugins.
As a test I checked the website with domain starting with myfa and there is Types 3.3.8 installed, despite the warning hover hint in Toolset Dashboard which shows it is version 3.1.2 !
3.2 was out on Nov 29, 2018 and I always update in at most a week...
So this data in Toolset Dashboard is incorrect, I know I updated all my sites, so this is clearly incorrect, so it can also be incorrect in other areas.
d) I honestly dislike the Toolset (and WPML) site registration method, when http and https is different and hidden link and domain.com is also different, requires different keys.
I think it causes more wasted time and frustration for us, clients and more support load for you...
There are lots of questions in this thread, I am trying to answer them one by one.
a) so something has changed recently (weeks or months ago?)
Yes, the installer feature is embedded in Toolset Types plugin, you can check the change logs here:
https://toolset.com/download/toolset-types/#changelog
There are some recent items related, for example:
- Updated the Installer component to address further WordPress 5.3 compatibility issues.
- Updated the Installer component to ensure compatibility with WordPress 5.3.
b) I linked 2 issues in my original post and I suppose they might be different indications of the same reason.
The third one is not related, please check my answer in that thread:
https://toolset.com/forums/topic/settings-change-for-a-post-field-field-group-is-not-changed/#post-1414411
c) If you check my Toolset Dashboard / Sites at ...
I can not see your "Toolset Dashboard / Sites", this is private message.
But since I can get the duplicator package from the new thread, so I have test it in my localhost, with below steps:
1) Get the Toolset site key with the new URL of my localhost: hidden link
2) Setup the site key according to our document:
https://toolset.com/faq/how-to-install-and-register-toolset/#installing-the-toolset-types-plugin
Then go to Toolset Dashboard / Sites, I can see it works fine, see screenshot dashboard.JPG
d) I honestly dislike the Toolset (and WPML) site registration method ...
Yes, it is expected result, since http and https are using different port: 80 and 443, we can use them to setup different websites, so when you generate the site key, it is required to input the full URL of your website(including http or https in the URL).
re: a:
I don't care the specific changes if it doesn't cause issues. But thank you.
re: b:
I supposed the issues might be related, therefore I informed you about it, trying to help you to view it from higher perspective.
re: c:
I attach 2 screenshots which shows warning icons for Types, what shows I use on those sites v 3.1.2, meanwhile I use latest 3.3.8 on all (detailed in c )
So there must be some issues in Toolset's system, what might be related to subtopic a.
I also upload my WPML dashboard screenshot, where you can see similar issues shown.
Also it shows the sites are not registered, which is clearly not true, they were registered and they are all up-to-date .
Furthermore you can see the licensed URLs are inconsistent: in Toolset http / https is included, in WPML it isn't...
re: d:
I understand you, but I dislike it, it causes more issues than benefits, and WPML and Toolset is inconsistent, which is a huge NO for me.
Thank you
Addition to c:
regarding comment of WPML screenshot:
I was wrong, those sites are registered, you can ignore that part of my comment.
I was confused by the content of column "End-user accounts".
But it shows incorrect info about versions installed.
My bad, sorry.
For the new questions:
Q1) I was confused by the content of column "End-user accounts".
That means there isn't other Toolset user account using the URLs, you can invite your customer to setup a individual Toolset account
Q2) But it shows incorrect info about versions installed.
In my test, it works fine, see screenshot I provided above:
https://toolset.com/forums/topic/staging-copy-issues/#post-1414471
As I mentioned above: the installer feature is embedded in Toolset Types plugin
You can try these:
1) Upgrade Toolset Types plugin of all websites to the latest version manually,
2) Regenerate/setup the site keys and test again:
https://toolset.com/faq/how-to-install-and-register-toolset/
If you see my screenshots, it shows that dates
after 13 Dec shows correct info,
dates before 4 dec shows incorrect,
so that your dashboard screenshot shows correct info of
date 18 Dec
is not a surprise and I hope you understand that you having correct data not means
all we Toolset users, who have registered sites from before might not have the same I have.
Checking the changelog 3.3.8 was issued on 10 Dec, and seeing 3.3.7 was issued on 7 Nov, I'm pretty sure my issue is related to 3.3.7,
the issue not been existed months ago.
So I update you with the latest, checking again all:
- I have Toolset Types 3.3.7 on my staging2.*** website
- I can't update it, having:
"Toolset Types cannot update because your site's registration is not valid. Please register Toolset again for this site first."
- on Toolset it was registered
- now I could use the key and register this staging2 website, download Blocks, update plugins
- but I can't update WPML plugins, having the same message about I have to register it again...
- switching to staging1: it already had Types 3.3.8 and I could update Toolset plugins,
but again I couldn't do it with WPML (having v4.3.5)
- switching to live site of the same domain, Toolset plugins are up to date.
Checking Toolset Dashboard on Toolset page Toolset versions look correct now for both staging subdomain, but not for the live domain!
I suppose it would be refreshed if I'd enter again the reg key, but I don't care, I want to keep working on MY stuffs and not on debugging.
So my conclusion:
- the issue originally reported was fixed with Types 3.3.8 and after re-registering sites, entering and saving license keys AGAIN.
- the issue still exist for WPML, I suppose I have to re-register my sites again... This version is 4.3.5
I'll close ticket in some days, assign it back to me pls.
Thank you
OK, I have marked this thread as "Waiting for feedback" status, so it can keeps open, you can update here if you need more assistance for it. thanks
My issue is resolved now. Thank you!
