Hi Support
This is not a ticket regarding Toolset itself, rather the support forum. It is currently not possible for me to view old support tickets. I always get a firewall error.
Below is what I see when I click the link.
Thanks and regards
Simon
Oops, our firewall is edgy today
Your visit to toolset.com looks has raised a flag to our security system. Don't worry, this is probably a false alert. Please contact us and enter the content of the block details box below. We'll add you to our whitelist so that you can continue accessing toolset.com normally.
If you can't use our contact page (because you're getting blocked), please visit our Facebook page and send us a message.
Block details
Your IP:
xx.xx.xx.xx
URL:
https://toolset.com/forums/forum/professional-support/
Your Browser:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.163 Safari/537.36
Time:
2020-04-29 03:22:26 -0500
Hello and thank you for contacting the Toolset support.
I reach out to our system team for this issue and we would like you to test again from a different browser, and also from a different connection(phone network).
Looking forward to your reply.
HI Jamal
I only have one network at home. But I tested also on a Windows PC with Edge via a company VPN. Same results.
It is happening on Safari, Chrome, Firefox, MS Edge.
Safari:
Your IP:
xx.xx.xx.xx
URL:
https://toolset.com/forums/forum/professional-support/
Your Browser:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
Time:
2020-04-29 09:28:08 -0500
Firefox:
Your IP:
xx.xx.xx.xx
URL:
https://toolset.com/forums/forum/professional-support/
Your Browser:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0
Time:
2020-04-29 09:29:24 -0500
Edge:
Your IP:
xx.xx.xx.xx
URL:
https://toolset.com/forums/forum/professional-support/
Your Browser:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 Edge/18.18362
Time:
2020-04-29 09:32:34 -0500
Kind regards
Simon
Hi Simon,
I tested also on a Windows PC with Edge via a company VPN. Same results. Do you mean a browser extension or a remote machine?
As you are the only user to having this issue, our system team would like a confirmation that you are encountering the issue on a different connection/network.
If yes, we would like to know:
- IP Address
- Internet Provider
- Country
Your next reply will be private to let you share credentials safely.
I wonder if for your all tests you were on the same VPN! Maybe the VPN is contributing to the issue. Can you test without it?
HI Jamal
That's weird that I'm the only one 🙂
My IP is: 84.59.110.130.
The IP that I got back from my client's PC, which I have here physically at home, using a VPN via Pulse Secure, is 46.18.62.65, but I never use that PC for my Toolset work. I just did a test there because it was a Windows PC and wanted to test with an MS browser. It is only important that it works from my IP.
Regards
Simon
Provider is Vodafone in Germany
Hi
No, I don't use VPN otherwise, only on the Windows PC to dial into the company network. But all my Toolset stuff is on my regular home WiFi without VPN
Cheers
Simon
Thank you Simon,
Let me check this with our systems team and get back to you.
Our system team is still investigating this issue. As a workaround, you can visit your user profile page in a private browser window(logged off) https://toolset.com/forums/users/simonm-5/
You will have all your created support tickets.
I'll get back to you as soon as we find something.
HI Jamal
This looks like it is working again, but I didn't get any update from you. Is it permanently fixed?
Thanks and regards
Simon
Hello Simon,
I just reviewed the internal ticket about this issue on our system and it is still a work in progress, but it seems that the system team has fixed it for you, my apologies for missing that and not getting back to you.
The issue was caused by some shortcodes samples being written outside of tags, these shortcodes were causing too much CPU and memory for some pages.
Best regards,
Jamal
HI Jamal
OK, no problem. I'm always happy when there's a solution. 🙂
Regarding my other open ticket with you, did you receive my update? I'm not sure if you did since the status was set to "Fixed in next release". If you get a moment, I'd appreciate an update on that.
Thanks and regards
Simon
Hello Simon,
Indeed the fix was also released on this week's update. I tested it on my local copy and it works no 404 errors or fatal errors on the homepage when pages and posts are managed by Toolset. The WPML root page should be public though, otherwise, guest users will get a 404 on the root URL.
Best regards,
Jamal
My issue is resolved now. Thank you!
