https://netsuiteprofessionals.com logo
Join Slack
Powered by
Hi – if your SuiteCommerce CMS pages and blog post...
# suitecommerce
s
Hi – if your SuiteCommerce CMS pages and blog posts are still not working, could you please check your configuration record and add CUSTOMRECORD_SC_BLOG_PAGE_TYPE_POST to the Integrations > CMS Lazy Loading section. Then save and cache clear, and let me know if that works. EDIT: Basically, I think there is still a permissions error in the blog extension somewhere, and what this is doing is telling to defer loading blog posts until later. This means that other CMS content (such as landing pages) has time to load before the blog posts run in trouble. So, this is a workaround, not a fix.
✅ 2
🙌 1
This setting is also available in SCA 2022.1.1+
s
Updated the config, saved, and cleared the cache - still no dice on my end, CMS HTML content areas not loading 😞
s
I've not heard of CMS HTML content areas being problematic. You got a case for that one?
m
@Shelby Owens let me know if you want to connect and go over the fix
It worked for me on 3 different accounts
s
Yep I have a re-opened case - they closed it on Tuesday but those areas are still not loading for our sandbox site
s
Ah sandbox is different
I don't think we've rolled out all changes to SBs yet
m
Oh yeah
s
Ahhhh okay, no worries then! I will continue to wait haha
m
Thanks Steve! Is there any workaround for SCA 2022.1.1 previous versions?
s
I think disabling the ext-blog-post CMS page type might work
m
It worked 🙌, but what about the blog post? Is there going to be a new update for the Blog ext or a patch to be applied into SCA in order to get them working?
s
Working on it
u
Thanks @Steve Goldberg and to your team as well!
r
Thanks for this Steve. I just reported an issue yesterday regarding SC Stock Notifications.
m
Blog posts started working but not the CMS pages.
m
You can create a custom role, and give full access to those blog records. Go to PageTypeSettings.ss service, enable permission, and assign that role. This is the custom record that should have full access CUSTOMRECORD_SC_BLOG_PAGE_TYPE_POST.
This is not official @mesper but that's what I did and it works.
Make sure you enable the checkbox to allow not logged-in users or something, I don't remember exactly the verbiage.
m
@Martin Da Rosa Thank you! That's for the cms pages right? I am a bit lost now..
m
For blog posts pages
If you go to a detail blog post
It won't work till you do this
m
@Martin Da Rosa Alright, thanks for your help!!
🙌🏼 1
r
@Martin Da Rosa Thanks for sharing! I tried this alternate solution in SC Stock Notifications -- however it does not work. Looks like I need to wait for an actual fix.
m
What's the issue you are experiencing @Regorr Segarra?
u
Also gave this a try @Martin Da Rosa but it just shows internal Error - and network tab (on chrome dev tools) on pagetype.ss still showing permissions issue
m
Try adding the record to that lazy section in the config record
@//greg your issue is that you are still unable to see the blog detail pages?
u
yea
r
ERR_INSUFFICIENT_PERMISSIONS as well when trying to get notified for stock notifs.
m
Did you create a new role and assign those permissions I mentioned? And went to the pagetype.ss service enabled permissions and set that role, also checked the option for Run the script without login?
I attached a screenshot
u
image.png
m
You should go to Customization > ssp applications and find the ssp for the ss2 services
And that blog post role has this permissions under custom record?
@Regorr Segarra identify what service is throwing that error first
u
@Martin Da Rosa
r
Yeah, it's the Subscription.Service.ss which I had my elev permission and the role has Full access to the record being used by that service and model.
u
Customer Center role ok to set it up with ?
m
Yes @//greg. Can you try elevating the permissions for the other records and test?
And send me a screenshot of the message that the pagetype service is throwing
@//greg you are in prod correct?
u
yes ^
m
Ok, please try that and let me know
Also please throw me the error message from the pagetype service
u
image.png
m
Are you sure you are giving the permissions for the right file correct?
If you could send the url of that pagetype service and the ssp of the file you are updating would be great
u
Yea its all correctly set up like you said but still throwing this error above. I set it up incorrectly first on the Development Folder but then you mentioned set it up on Development2 folder and i did that but yea still having an issue - can you share your custom role you created ?
m
Screenshot 2024-08-22 at 3.15.17 PM.png
w
We are experiencing this on multiple accounts. Reading through this thread and will attempt the suggestions.
u
My error was I set up my custom Role as a customer Center not “Classic center” like @Martin Da Rosa’s. Thanks Martin for all the help!
🙌🏼 1
m
The Center type of the custom role needs to be Classic Center
No problem @//greg! Anytime man
@Will Little let me know if you need any help.
w
@Martin Da Rosa Your suggestion did not work for one client I'm testing. They are on 2020. I cannot find pagetypesettings.ss I can find pagetype.service.ss
The Lazy Load solution works for clients on 2022 so far in my experience. But older clients I need another solution
m
So adding that custom record type to the lazy load section on the configuration record and clearing cache did not fix landing pages?
w
That DOES work, but clients on earlier versions, there is not the lazy load section to add the record.
So I attempted your other solution, but cannot find pagetypesettings only pagetypeservice
m
Their extension managed is on 2020?
manager*
w
SCA version of 2020 in this case
m
Right
w
extension managment is the current version 2024.1
m
@Steve Goldberg might know more about that...
w
SC configuration is 2021.1.1
m
Can you send me the url of your website so I can check on my side?
w
@Martin Da Rosa DM
s
I have been told that going to Commerce > CMS Page Types and deactivating ext-blog-post also works as a temporary fix
✅ 2
m
@Steve Goldberg can confirm -- just worked for me on 2024.1.1 Standard SC instance.
w
@Steve Goldberg I can also confirm The Lazy Load fix works for newer instances. Disabling the ext-blog post works for older ones. Having the blog down temporarily isn’t great, but it’s better than not having any landing pages load.
👍🏻 1
s
The team are working on it. Right now, we have a number of extensions that rely on code that creates records (often only to enumerate their fields), so the team are working out the best way to handle this, whether it is to find a way to give those scripts permissions to create records in particular contexts, or to replace it with code that doesn't need to do that. It is a bit tricky.
n
@Steve Goldberg I deactivated CMS Page Type and that removed the 404 Page Not Found Error, but the page content didn't load. Are these fixes for PRD or SBX? I am in UAT with a client right now weeks before go live and we cannot test in SBX. What can we do?
The lazy load addition also removed the 404 Page Not Found error, however, the page still loads empty. No page content is shown.
m
All those fixes applies ONLY for prod @Nicholas Cole
Are you experiencing issues on the landing pages? Will you be able to share a URL with me, please?
You can check if the pagetype service is able to get the data from NS or is throwing a permission issue
v
Hi i too getting the same issue My SCA version is 2020.1. I am getting a page not found error when I navigate to any CMS page. Anyone know what the reason is?
m
@VS the issue is the permissions update Netsuite did. @Steve Goldberg should be able to speak more about it.
Right now, that's the workaround for by-passing that issue.
l
@Steve Goldberg How come we are only having an issue when customer is logged out. The moment they login, cms content loads fine.
m
@Livio because it's a permission issue.
l
CUSTOMRECORD_SC_BLOG_PAGE_TYPE_POST i added this to configuration but it didnt make a difference
m
Are you able to see CMS content? But not the detailed blog pages?
l
im not able to see CMS content at all @Martin Da Rosa when customer is logged out
n
Is there any update on a fix for sandbox sites?
c
I have a customer who doesn't have the blog extension and cannot see CMS content unless users are logged in. This is the error message coming from the 
api/cms/v2/contents
endpoint: 
Content on this page is missing crucial information. This can happen if you manually edit or delete content records in NetSuite. To correct the problem, in NetSuite, delete the CMS content record with ID 37 and use Site Management Tools to add the content back to the site.
m
@Chris you will need to give more rights to the page type service. Enable permissions, assign a role and elevate permissions over the blog custom records
That's the way I fixed it and I'm fixing websites
c
The pagetype.Service.ss file is locked.
m
You are on suitecommerce standard
👍🏻 1
Ok, nothing to do then
If you really want to fix it, you can overwrite and setup CMS to use a different service and enable permission for that one... @Chris
But it's a lot of work... it depends on how much you want to invest on it
n
@Steve Goldberg I have a GO live at risk due to this CMS 404 Error on Sandbox. Is there a permanent fix in sight for this issue? What workarounds are there for Sandbox so we can continue with our UAT?
m
@Nicholas Cole you can create a staging environment in production and test it there
And it will decrease the risk
Is your customer live on NetSuite?
n
That's what I was thinking. No, they are not live yet. I just floated out deploying to production and completing UAT there.
s
We are prioritising production environments; I agree, that if you're preparing to go live then it would make sense to do UAT on a production environment
m
Yeah, that will decrease risk and increase go-live preparation @Nicholas Cole
👍🏻 1
s
It was a national holiday yesterday, so I am trying to catch up on what exactly the differences are between sandbox and production environments right now. What specific things have you noticed?
m
Based on what I heard, the main issue is that the hotfix, adding the custom record type to the lazy load is not fixing it
v
@Martin Da Rosa Adding the custom record type to the lazy load did not fix it in older versions of SCA (2020.1) because that lazy loading code is not there in the SCA source code module.
n
Yes, none of the fixes that work in Production work in Sandbox.
m
For those with SuiteCommerce standard and blog detail pages not working please reach out and I will walk you through the fix I found!
🙏 2
l
hey guys, if you are having issues with CMS html content on the site, it seems like all custom record types, that are set to "No permission required", need to be updated to "use permission list", or "require custom record entry permission" that should fix the issue.
m
Is there still no NS resolution for this?
c
For the most part, it seems like the permissions issues are solved. But, in one account I worked on, someone that was troubleshooting disabled the CMS module entirely and never turned it back on. The customer says they didn't do it.
169 Views
Open in Slack
PreviousNext
Powered by