I will review the whole process:
1. The site is hosted on SiteGround.
2. Our SiteGround account has a staging server function.
3. The staging server function creates a clone of the production site.
4. We are rebuilding the site theme, not the functionality, so we set up a staging server with a clone of the production site.
5. All other plugins, including paid plugins, made the switch to the staging server just fine. This is not true of Toolset.
6. I first found a problem when I tried to add Blocks to the staging site. I could not add Blocks without adding a new address to the account, even though it has the same domain name.
7. I added the new address to the Toolset account.
8. The instructions indicated that I needed to re-install Toolset Types.
9. I asked tech support if two copies of Toolset Types could co-exist. I said that it was a clone in the ticket. The response was that yes, that was possible.
10. Even with the new install, Toolset threw an error because it needed a new code.
11. There was no way to enter the new code without removing the original Toolset Types install, which I did.
12. Now, the inside pages do not work.
Hello and thank you for contacting Toolset support.
I am really sorry, but I still do not understand the real issue. What do you mean by "the inside pages do not work"? Can you share URLs? Or screenshots that include the URLs?
(the URL can give us more context, and we can now if it is a page in the backend or the frontend. If it is a view or an archive template, etc.)
Regarding 6. keep in mind that, for the Toolset registration kays, the following URLs are for different sites, and will require different registration keys(even though it is a staging site):
- hidden link vs hidden link
- hidden link vs hidden link ( notice the s in hidden link)
Regarding 9. You can't have two copies of the same plugin running(For example Types 3.4.13 and Types 3.4.14), would you show the ticket where we told you so?
After explaining the real issue that you are encountering(my first question) would you allow me temporary access to your staging site to check it further? Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **
REPLY ITEM 1:
"What do you mean by "the inside pages do not work"? Can you share URLs? "
The URL in question is hidden link. Inside pages are those pages that are not the home page. After trying to resolve the problems with Toolset Types, no inside page works.
An example of an inside page is hidden link
REPLY ITEM 2:
'Regarding 6. keep in mind that, for the Toolset registration kays, the following URLs are for different sites, and will require different registration keys(even though it is a staging site):
- hidden link vs hidden link
- hidden link vs hidden link ( notice the s in hidden link)"
Please note #7 in my original itemed listed: 7. I added the new address to the Toolset account.
REPLY ITEM 3:
"Regarding 9. You can't have two copies of the same plugin running(For example Types 3.4.13 and Types 3.4.14), would you show the ticket where we told you so?"
https://toolset.com/forums/topic/how-to-add-toolset-to-a-clone/
The problem could have been resolved much more quickly, if Wagar had asked some critical questions:
1. Have to added the staging site to the list of sites in your account?
2. The staging site will need a new key.
3. To add the key, go to ...
REPLY ITEM 4:
I will send the login information in a private reply.
The system will no longer allow me to send a private message with site credentials. Now, I can only send a regular reply.
The system does allow to add private replies only to the next reply. I am setting your next reply to be private. ** Make a database backup before sharing credentials. **
Once I get the credentials, I'll check why the following page is not working(blank page).
If you want me to check another page too, please add it to your next reply.
It looks like the problem is only affecting category pages.
We are rather concerned that there has been no reply on this issue. The problem is holding up our work. So, I did some code checking on my own and found out that there is an inline style that is causing the category pages not to show.
.date, .category, .tags, .author, .comments
{
clip: rect(1px, 1px, 1px, 1px);
height: 1px;
position: absolute;
overflow: hidden;
width: 1px;
}
This is deliberate code to hide the pages. It showed up at the same time that we attempted to set up Toolset Types on the site. I can understand if it is being used to protect your software from being abused, but we have a legitimate account.
Hello and my apologies for the late reply, but I do not work on Wednesdays and Thursdays as you may check on my profile page https://toolset.com/forums/users/jamal-b/
I agree, the issue is most probably caused by that CSS rule. However, this is not coming from Toolset. WordPress by default will add the taxonomy slug as a CSS class to the body in an archive template.
This page is an archive for the Categories taxonomy, so, WordPress will add the class "category"(it is the taxonomy slug) to the body. And the snippet does hide an element with the class "category". The whole body gets hidden.
This snippet is not added by Toolset. It seems to be added with the "spacious_style-inline" handler. Check this screenshot hidden link
I could not find the code that could be responsible for it in the child-theme code. The child theme is called "Goosebay Spacious". I am keen to think that it was added by the child theme's code, but I could not find where. Maybe on the parent theme or on a separate plugin, but I could not find where.
From the CSS rule, I understood that it was meant to hide the author, date, categories, tags, and the comments link for a post. Check this screenshot after manually deactivating the rule hidden link
I also noticed that we can configure that from the theme's option in the customizer, in two possible options, more specifically here hidden link
Why not using the theme's options rather than custom CSS code. Please try to find what adds that CSS code and disable it.
I'll remain at your disposal.
