813 comments found.
Clarification on License and User Roles in Civi Theme
Hello,
I hope you’re doing well.
I have a few questions regarding the Civi theme:
1. License Clarification
Is the Regular License sufficient to allow employers to purchase job packages and post jobs on the website? Or is an Extended License required for this functionality?
2. User Roles (Employer / Candidate / Freelancer)
Currently, I only see two registration options: Employer and Candidate.
How can freelancers register and log in on the platform? Is there a built-in option for freelancers, or should they register under a specific role?
I would appreciate your guidance on these points.
Thank you in advance for your support.
Best regards,
Nuhman Nathly
Hello,
Thank you for reaching out and for your interest in the Civi theme.
Regarding your questions:
1. License Clarification The Regular License is sufficient for allowing employers to purchase job packages and post jobs on your website. You do not need an Extended License for this functionality.
2. User roles:
Civi is designed to support both Job Board and Freelance Marketplace use cases within the same theme.
The Candidate role is primarily intended for users in a Job Board scenario — meaning individuals who are looking for jobs posted by employers. In a Freelance Marketplace scenario, these same users (Candidates) effectively act as Freelancers, offering their services and applying to projects posted by employers.
In other words, there is no separate “Freelancer” role because the Candidate role serves both purposes, depending on how you configure and position your platform:
Job Board → Candidate = Job Seeker Freelance Platform → Candidate = Freelancer
This flexible approach allows you to run either model (or even a hybrid) without needing additional user roles.
Best regards,
Thanks for the update
Can we give the CV package to employers so that they can see CVs based on the package they are activating?
Is there a resume builder available for candidates that is accessible via the candidate dashboard?
If yes, can we make the resume builder public so that anyone can create a CV without logging in?
Hello,
Thank you for your questions.
1. CV Package for Employers Yes, you can assign CV/Resume packages to employers. Based on the package they purchase, employers can access candidate profiles and resumes according to the limitations defined in each package.
2. Resume Builder for Candidates The theme allows candidates to create and manage their professional profiles (resumes) from the Candidate Dashboard.
However, please note that this is not a standalone “resume builder” with customizable templates. Instead, candidates create their resumes by filling in structured profile fields such as experience, education, and skills.
3. Public Resume Builder (without login) By default, this functionality is only available for registered users, as all resume data is tied to user accounts.
Best regards,
Thanks and soon to be a partner with Uxper.
I have some pre-sale questions: 1 – Does the theme allow applying for a job by simply attaching a resume without needing to create a profile or add any additional information? 2 – Does the theme allow posting a job without needing a company profile?
3 – Is it possible to add custom fields to the job posting forms or company/candidate registration forms?
4 – Is it possible to hide the photo upload field from the candidate profile?
Hello,
Thank you for reaching us. For your questions:
1. Yes, our theme support that. It’s possible to use the login-free application function.
2 and 3. Our theme does not support that at the moment. If you needs we can help you customize.
Regards,
I watched the review https://www.youtube.com/watch?v=bGuwT2YpxUI
At minute 23:12, custom field menus appear:
custom field (jobs)
custom field (company)
custom field (candidate)
Do these fields no longer exist, or do they have a different purpose?
Is it not possible to obtain a trial version of the theme to look inside WordPress? Because the demo version only shows the external interface.
Hi there,
Thank you for your questions!
At the moment, we do not provide a demo with access to the WordPress admin dashboard. The available demo is intended to showcase the frontend only.
Regarding the custom fields (Jobs, Company, Candidate): These are not traditional standalone “custom fields” in WordPress. Instead, they are built into the theme’s custom post types and are managed via the theme’s core plugin (e.g., Civi Core).
Each post type (Job, Company, Candidate) has its own structured set of fields inside the edit screen in the WordPress admin. These fields are used to store and display specific data such as job details, company info, candidate profiles, etc.
So instead of finding them under a generic “Custom Fields” section, you will work with them directly when editing:
Jobs → job-specific fields
Companies → company-specific fields
Candidates → candidate-specific fields
Thank you,
Hello dear Uxper team
please new updates for freelancer features Thanks Regards
Hello,
Thank you for your suggestion. We are continuously improving the freelancer features, and new updates will be released in the upcoming versions.
Please stay tuned for future updates.
Best regards,
Hi, I’m considering buying this theme. However, I have one question about the licence type. The core of my project is job and career management, for which the platform is free. But I also want to create a community through Buddy Boss and GamePress, and I’m thinking of having subscription levels for that. As far as I know, this is compatible with a regular licence, right?
Hello,
Yes, that’s correct. A Regular License is suitable for your use case. You can build a free job & career platform and monetize other parts of the site (such as community features via BuddyBoss and GamePress) through subscriptions, as long as you’re not reselling the theme itself.
Regards,
This is not a support request but a reproducible core bug.
When clicking Share Job → LinkedIn, the page crashes with: URIError: URI malformed at decodeURIComponent()
This happens only when sharing individual job posts, not footer links or Facebook sharing. It worked before recent updates / security cleanup and is now reproducible on multiple jobs.
Root cause: The share function applies decodeURIComponent() on a URL that is already encoded (or has been modified by filters/security). This results in a malformed URI and LinkedIn fails while parsing query parameters.
Evidence:
The LinkedIn URL already contains a properly encoded url= parameter
Calling decodeURIComponent() again throws URI malformed
Facebook sharing works (no decode step), so this is not a LinkedIn limitation
This is a code-level issue, not configuration.
Suggested fix (minimal & safe):
Ensure the job URL is encoded exactly once
Remove decodeURIComponent() from the share logic, or guard it with try/catch
Use encodeURIComponent(window.location.href) when building the LinkedIn share URL
This can be fixed directly in the theme / framework JS and does not require site-specific customization.
Please acknowledge this as a bug and include a patch in the next update.
Hi,
Thank you for the clear analysis and reproduction steps — we’ve reviewed this and agree this is a core bug, not a configuration or LinkedIn limitation.
You’re correct: the LinkedIn share logic currently applies decodeURIComponent() on a URL that may already be encoded or modified by security filters, which can result in a malformed URI and cause the crash you described. This also explains why Facebook sharing is unaffected.
We’ve acknowledged this internally and will:
Ensure the job URL is encoded exactly once
Remove or safely guard the decodeURIComponent() call
Build the LinkedIn share URL using encodeURIComponent(window.location.href)
This fix will be included in the next update. ETA: within the next release cycle (hotfix if possible).
Thank you for reporting this with such precise technical detail — it helped us validate and prioritize the fix quickly.
Best regards,
Thank you for the confirmation and the detailed response. We appreciate that you’ve acknowledged this as a core bug and confirmed the root cause.
The proposed fix sounds correct and aligns with our findings. We’re glad to hear it will be included in the next update (or a hotfix, if possible).
Thanks again for the quick review and professional handling of the issue.
Hello,
Thank you for your understanding and confirmation. We appreciate your feedback and are glad we’re aligned on the root cause and solution. The fix will be included in the upcoming update (or a hotfix if feasible). Thanks again for your patience and cooperation.
Regards,
LinkedIn job sharing no longer works – URIError: URI malformed (after malware cleanup)
Ticket Description Hello Civi Support Team,
we are using the Civi Job Board theme and have an issue with sharing individual job ads on LinkedIn.
Before a recent malware/spam cleanup, the LinkedIn sharing worked perfectly. After the cleanup, sharing a specific job post to LinkedIn fails with the following error on LinkedIn’s side:
URIError: URI malformed at decodeURIComponent
Important notes:
Sharing the page itself works
Footer LinkedIn links work
Facebook sharing works
The issue only occurs when sharing individual job ads
This worked correctly before the cleanup
No custom sharing code was added by us
Based on the error, this looks like a URL encoding / query parameter issue (possibly double encoding or filtered parameters), not a general LinkedIn limitation.
Could you please advise:
Whether this is a known issue with Civi job sharing
If there is a recommended fix or code snippet
If job share URLs should be sanitized or encoded differently for LinkedIn
We are happy to apply a fix via child theme or custom plugin if needed.
Hi,
Thank you for the clear analysis and reproduction steps — we’ve reviewed this and agree this is a core bug, not a configuration or LinkedIn limitation.
You’re correct: the LinkedIn share logic currently applies decodeURIComponent() on a URL that may already be encoded or modified by security filters, which can result in a malformed URI and cause the crash you described. This also explains why Facebook sharing is unaffected.
We’ve acknowledged this internally and will:
Ensure the job URL is encoded exactly once
Remove or safely guard the decodeURIComponent() call
Build the LinkedIn share URL using encodeURIComponent(window.location.href)
This fix will be included in the next update. ETA: within the next release cycle (hotfix if possible).
Thank you for reporting this with such precise technical detail — it helped us validate and prioritize the fix quickly.
Best regards,
Hi,
Currently, https://civi.uxper.co/?s= shows many results that shouldn’t be visible. When will this be fixed?
Hi,
The search results shown on this page include all available post types by default, which is expected behavior.
To restrict the search to a specific post type, simply add the appropriate post_type parameter to the URL.
Let us know if you need help setting this up.
Regards,
Thanks for your reply, however this does not address the actual issue.
The search results currently expose content that should not be publicly accessible, including:
- private user messages, https://drive.google.com/file/d/1GMEifygXB57Q2aDuVj4gxGqPQCuoTRQH/view?usp=sharing
- email addresses from job alerts emails and similar notifications (potentially containing sensitive data). https://drive.google.com/file/d/1_xFTyO49OwlMg1R6E4Ks_0mziDKSkSZl/view?usp=sharing
- notyfication
- user_package/ etc
This is not simply “expected default behavior” — it is a serious privacy/security issue and can lead to unintended disclosure of sensitive information.
Please clarify urgently:
Are you notifying customers who purchased and use this theme that sensitive/private data may be exposed through the search results?
What exact steps will you take to fix this, and what is the ETA?
Will you publish an official security update / advisory regarding this issue?
This has major legal and reputational consequences for site owners, so it should be treated as a critical issue and fixed as soon as possible.
Hi,
Thank you for reporting this. You’re absolutely right — exposing private or sensitive data via search results is not expected behavior and must be treated as a critical security issue.
Our initial investigation shows this is caused by insufficient restrictions in search indexing/query handling, which can allow non-public data (messages, notifications, user-related endpoints) to appear in results. This is not intentional, but the impact is real.
Actions in progress:
Excluding all private/system/user-related data from search results
Enforcing access checks to prevent exposure even if indexed
ETA:
Hotfix: 24–48 hours
Full security update + advisory: within 3 business days
Yes, customers will be notified once the fix is released, and an official security update/advisory will be published.
We understand the legal and reputational implications and are treating this as a top-priority issue.
Best regards,
Hi,
Thank you for your previous response.
However, the promised 24–48 hour hotfix and the full security update within 3 business days have already passed, and the issue still appears to be present.
Could you please provide an immediate update on the current status of the fix and a confirmed timeline for when this vulnerability will be fully resolved?
Given that this involves exposure of private and sensitive user data, the delay is very concerning. Please also confirm what temporary mitigation measures, if any, have been implemented to prevent further data exposure.
I would appreciate a prompt and transparent update on this matter.
Best regards,
Hi,
Thank you for your follow-up and for your patience.
The issue has been resolved in version 2.2.5.1. Please make sure to update both the theme and the Civi Framework plugin to the latest versions to ensure the fix is fully applied.
After updating, we recommend clearing cache (if any caching system is enabled) and verifying the site again.
Best regards,
Thank you for your response.
Could you please confirm whether the demo has also been updated and secured? https://civi.uxper.co/?s=
Hi there,
Thank you for your follow-up.
Yes, we can confirm that the demo site has been updated with the latest code and security fixes. The current version running on the demo (https://civi.uxper.co/?s=) reflects the most recent updates.
Best regards.
Any update ?
Hello,
Yes — the update will be released later today.
Thank you for your patience. We’ll notify you as soon as it’s available.
Regards,
Hi Uxper, Good Evening
I Hope you had review the below errors in CIVI THEME, and provide the solutionin the upcoming update.
1.) Candidate Profile & Company Profile Page Not Open With Cover/Thumbnail Image / Critical.
When a user uploads a Cover Image and then saves the candidate profile, the profile does not load afterwards. It only shows a continuous loading icon. I have tested this multiple times and confirmed that the problem occurs only when a cover image is uploaded. If I remove the cover image from the backend, everything works correctly, and the candidate profile loads in less than a second. Please look into this issue and help resolve it at the earliest.
2.) Email Colour Issue
The default text/heading colour in system emails is showing in green. We are unable to change these colours to match our website’s branding/colour palette. Please allow customisation or fix the default style.
3.) Signup Form Placeholder Issue
In the signup form, both the First Name and Last Name fields are showing the same placeholder “Name”. The placeholders should correctly display “First Name” and “Last Name” respectively. This is a small detail, but users easily notice it. Please look at this image https://www.awesomescreenshot.com/image/57451829?key=a16f4bb27f4d8dffa332043fe12f6e49
Hello,
Thank you for reporting these issues and for the detailed explanations.
We have reviewed the points you mentioned regarding the candidate/company profile cover image, email color styling, and the signup form placeholder. Our technical team will investigate these issues carefully and include the necessary fixes and improvements in an upcoming update.
We truly appreciate your patience and feedback, as it helps us improve the theme quality. We will keep you informed once the update is ready.
Best regards,
Hi Uxper, good evening.
I want to highlight a major concern that needs to be reviewed.
Currently, on both the candidate archive and company archive pages, whenever a new candidate registers, the older candidates get pushed down the list.
The same happens for companies — when a new company registers, the older ones automatically move to the bottom. There is no algorithm controlling the listing order. Even a simple method like shuffling the list on every refresh would be better.
What do you think about this? It should be fixed.
Hello,
Thank you for your feedback.
This behavior is actually the default sorting method of WordPress, where newly created posts (candidates/companies) appear first and older ones are pushed down. However, we completely understand your concern, and we will review your request to see if we can add an option for different listing orders (e.g., random shuffle, custom sort, etc.) in a future update.
Thanks again for bringing this to our attention. Let us know if you have any other suggestions.
Regards,
Hi, In the email template in admin email, when a new user registers, does the shortcode %user_email_register work for you?
When a new user registers, I receive an email, but the shortcode %user_email_register does not display the new user’s email.
Hello,
Thank you for reporting this issue.
We’ve checked the registration email template and can confirm that the shortcode %user_email_register is currently not working as expected. This is indeed a bug on our side.
Our development team has already added this to the fix list, and it will be corrected in the upcoming update.
Thank you again for letting us know — your feedback helps us improve the product. If you need a temporary workaround in the meantime, feel free to let me know.
Best regards,
Hi, Please add to the upcoming update an option to add taxonomy and category descriptions:
For SEO improvement, add the ability to include a description for categories and taxonomies under the archive results. This should apply to blog categories, tags, and candidate and employer locations.
The description should appear on the first page of the category, not on subsequent paginations (e.g., pages 2, 3, 4, 5). This is standard WordPress functionality and will significantly improve SEO.
Hello,
Thank you for your suggestion. We’ll review this request and consider adding it in a future update.
Best regards,
Hi Uxper,
Good Morning
1. Which cache plugin have you tested and do you recommend for the Civi theme?
2. Since the theme performs many live tasks—such as applicants applying for jobs, sending messages, candidate selection, scheduling meetings, and generating instant notifications where all updates need to reflect on the dashboard in real time—
is it safe to use a cache plugin? Specifically, can a cache plugin handle these real-time requests without causing delays or issues?
Good morning, and thanks for your questions.
We’ve tested Civi with LiteSpeed Cache and WP Rocket, and both work well with the theme. LiteSpeed Cache generally provides the best performance if your server supports it.
Yes, you can use a cache plugin safely. Civi’s real-time actions (job applying, messaging, notifications, scheduling, etc.) are handled through AJAX/REST requests, which are not cached, so they will continue to work normally.
Regards,
Okay, thanks for a quick response.
Hi Uxper, Good Morning
I believe that such an error coming from your theme/product does not require renewing or asking for support, as you know my support period has expired, and this error is not from my end. Please check below attached image below. This is from your default theme. And you should fix this instead of asking for a support ticket.
You can test this on your end.
Profile Not Open With Cover/Thumbnail Image / Critical.
When a user uploads a Cover Image and then saves the candidate profile, the profile does not load afterwards. It only shows a continuous loading icon.I have tested this multiple times and confirmed that the problem occurs only when a cover image is uploaded. If I remove the cover image from the backend, everything works correctly, and the candidate profile loads in less than a second. Please look into this issue and help resolve it at the earliest.
BELOW LITTLE BUT IMPORTANT
1.) Email Colour Issue
The default text/heading colour in system emails is showing in green. We are unable to change these colours to match our website’s branding/colour palette. Please allow customisation or fix the default style.2.) Signup Form Placeholder Issue
In the signup form, both the First Name and Last Name fields are showing the placeholder “Name”. The placeholders should correctly display “First Name” and “Last Name” respectively. This is a small detail, but users easily notice it. Please look at this image https://www.awesomescreenshot.com/image/57451829?key=a16f4bb27f4d8dffa332043fe12f6e49Hello,
Thank you for your feedback. We will verify the issues you reported and, if confirmed, address them in the next update.
Regards,
Thanks for your understanding. Please let me know if anything additional is required from my side.
Hi Uxper,
Good Evening, Pls check the critical error/bug in the theme and help to fix it asap.
Profile Not Open With Cover/Thumbnail Image / Critical.
When a user uploads a Cover Image and then saves the candidate profile, the profile does not load afterwards. It only shows a continuous loading icon.
I have tested this multiple times and confirmed that the problem occurs only when a cover image is uploaded. If I remove the cover image from the backend, everything works correctly, and the candidate profile loads in less than a second. Please look into this issue and help resolve it at the earliest.
BELOW LITTLE BUT IMPORTANT
1.) Email Colour Issue
The default text/heading colour in system emails is showing in green. We are unable to change these colours to match our website’s branding/colour palette. Please allow customisation or fix the default style.
2.) Signup Form Placeholder Issue
In the signup form, both the First Name and Last Name fields are showing the placeholder “Name”. The placeholders should correctly display “First Name” and “Last Name” respectively. This is a small detail, but users easily notice it. Please look at this image
https://www.awesomescreenshot.com/image/57447660?key=376ba5685078ff6234426db317ec8d0f.
Hello,
Please open a support ticket at https://uxper.ticksy.com/. Our support team will help you review and resolve the issue.
Regards,
I had reported a bug earlier as well. Please add an option to change the color of hyperlinks. Right now, any text that contains a link looks exactly like normal text, which causes confusion.
Hello,
This feature is already available. Please open a support ticket so we can provide you with detailed guidance.
Regards,
In the next update, please fix the following issues:
Missing field ‘postalCode’ (in jobLocation.address)
Missing field ‘addressLocality’ (in jobLocation.address)
Missing field ‘streetAddress’ (in jobLocation.address)
Missing field ‘employmentType’
Missing field ‘baseSalary’
Hello,
Thanks for your feedback. We’ve noted all the missing structured data fields you reported (postalCode, addressLocality, streetAddress, employmentType, baseSalary).
These will be reviewed and included in the next update.
Regards,
Hi Uxper,
I hope you’re doing well.
I was recently going through the comments on your platform to learn more about user experiences and came across the following conversition:
Candidate: What happened to the Sala theme? Uxper: Hi, we have stopped selling this product. It has been developed for a long time, and we do not update it anymore. Thank you.
Candidate: Your response is unacceptable. I purchased this product, which grants me a license to use it. Discontinuing sales or updates is your right, but deleting it for paying customers without any warning is a breach of your terms. I require either immediate access to the files I paid for or a full refund. Also, please clarify if my other purchases from you are at risk.
Uxper: Please rest assured that even though we have stopped selling Sala and no longer provide new updates, you can still continue using the theme normally, as it is already included in your account/license. Your existing purchase is not affected or removed, and you will always retain access to the files you have paid for. This only means we will not release future updates or new features for this product.
While I am not a user of the Sala theme, I am currently using the CIVI theme for my business.
My concern is straightforward — we rely on CIVI as a core part of our business operations and have invested significant time and effort into building on your framework. If you were to discontinue updates or support for CIVI in the future, it would put our business in a difficult position, especially since the theme’s framework makes it challenging to migrate elsewhere.
Could you please share your future plans for CIVI? Specifically, we’d like to understand whether continued updates, support, and long-term maintenance are part of your roadmap.
Thank you for your time and understanding.
Best regards, Vikas Rajput
Hello,
Thank you very much for your thoughtful message and for trusting the Civi theme as part of your business. We truly appreciate the time and effort you’ve invested in building on our framework.
Please rest assured — Civi remains one of our actively developed and supported themes. Our team continues to release updates, improvements, and compatibility patches with the latest WordPress versions and major plugins. We also maintain regular customer support through our official channels to ensure long-term stability for all users.
We have no plans to discontinue Civi. In fact, it’s one of our core products with ongoing development and feature enhancements based on customer feedback.
Thank you again for reaching out and for being part of our community. Your trust and feedback help us make Civi even better with each update.
Regards,
Hello I see you update today but what is new in this update?
Hello,
You can check the details of the latest update directly in your WordPress admin panel by going to:
Civi → Welcome → Changelogs
There you’ll find a full list of new features, improvements, and fixes included in the most recent version.
Regards,
Please consider adding some new features too! These themes are really good, but it feels like you’re limiting their potential. It would be great if you could include more features such as a resume builder, community options, and other useful tools to make them even better.
Hello,
Thank you very much for your valuable feedback and kind words! We truly appreciate your suggestions — features like a resume builder and community options sound great and would definitely add more value to the theme.
Our development team is already reviewing upcoming feature ideas, and we’ll consider including similar enhancements in future updates. Your input helps us improve, so please feel free to share any other ideas you’d love to see!
Regards,
hi my log in is not workig. how to fix this. plz reply ASAP.
Hello,
Please check the following points:
1. Ensure that both the Civi theme and Civi Framework plugin have been updated to the latest versions.
2. Verify that there are no custom codes causing the issue.
3. Make sure there are no third-party plugins creating conflicts.
If the issue still persists, please open a support ticket at https://uxper.ticksy.com/, and our support team will assist you in reviewing it.
Regards,
my code has expired. i can not open a ticket.
Hello,
If your support period has expired, you can easily renew your support license on ThemeForest to regain access to the ticket system.
Please go to your ThemeForest account → Downloads → find the Civi theme → click “Renew support”. After renewing, you’ll be able to open a new ticket at https://uxper.ticksy.com/ and our support team will assist you further.
Best regards,
