Norwegian language
Review the idea, its current status, and the latest conversation around it.
Menu
Support
Create Ticket
Your Tickets
Suggestions
Resources
FaQs
Dizzy - Support Creators Content Script
Answers to the most common Dizzy installation questions.
CreatorPulse FAQs
CreatorPulse onboarding, hosting and configuration answers.
Documentation
Dizzy - Support Creators Content Script
Membership and tip-based platform for creators who sell posts, livestreams and premium files.
CreatorPulse - Monetize Shortform Creators Subscription Paywall Live Video PHP Platform
Short-form video membership platform with live streaming, wallets, tips and pay-per-view drops.
Support Policy
Updates
Blog
ChangeLog
Dizzy - Support Creators Content Script
Latest Dizzy patches and feature drops.
CreatorPulse Changelog
CreatorPulse release history and improvements.
Norwegian language
Theme
Released
Submitted by promonde · Created 3 months ago · Updated 5 days ago
2
Votes
1
Comments
11 Feb 2026
Created
11 May 2026
Updated
2
Log in to vote
Provide the Norwegian language please
Progress timeline
Suggestion submitted
11 Feb 2026 · 3 months ago
Added to roadmap
11 Feb 2026 · 3 months ago
Released in product
19 Feb 2026 · 2 months ago
Discussion (1)
mstfoztrk · Support team
11 May 2026
This language file was added upon request.
Log in to vote, follow, and comment on this suggestion.
<- Back to suggestions
Welcome
Please log in to access your personalized support shortcuts.
Latest update
Dizzy v5.4 Update: Site Themes, Communities, Blog Tools, Messaging, and OBS/RTMP Support
Published 30 Apr 2026
Dizzy v5.4 introduces the new Site Theme infrastructure, expanded community and blog management tools, creator messaging…
Quick Help
Need guidance before opening or updating a ticket? Start with the most useful support resources.
FAQs
Documentation
Support Policy
Latest Changelog
Tips
Describe the expected result, the actual result, and the exact steps to reproduce the issue.
Add screenshots or a short clip whenever possible to reduce back-and-forth.
Mention the product, build/version, and whether the same behaviour can be reproduced on the public demo.
Support Guide
Priority replies are usually answered within 48 hours.
Use one ticket per issue so the conversation stays organized.
Add follow-up details in the same ticket instead of opening duplicates.
Reopen a closed ticket if the same issue continues.
Very rapid repeated replies may trigger short-term rate limits to keep the queue readable.