-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugs found in Fred (MODX 3.0.1, Fred 2.0.2) #452
Comments
There's a lot of unrelated things here. I'll try to cover these. We didn't change much if anything at all with the frontend on Fred for MODX 3 vs 2, the screenshots appear like you have some styling conflicts. Is your site in MODX Cloud? We may be able to take a look if it is there. It appears you have
not
The Open Settings block appears to be blocked by your styles. I'm guessing you have an overflow hidden or something going on there. We use Fred Import on a few sites in MODX 3, so I'm not sure why you are having issues without seeing your full call. I'll check for the FredTheme to see if an issue was introduced in the latest version. Modifiers will work, but without seeing your full call it's hard to tell what is going on. You may need to add an uncached value to the site_url attribute, e.g. [[!++site_url, since you are calling it within an uncached snippet. |
Thank you @matdave for your answer, you helped me a lot and prompted me to look for the reasons. I will write about each point. First, what is decided:
I have a suggestion for this. Maybe, it is worth writing down properties in the Fred styles, so that no one else has problems with positioning:
Failed to fix:
|
When creating a theme based on Fred, I noticed a few bugs (MODX 3.0.1, Fred 2.0.2):
Figure 1
Figure 2
"remote": "true"
creates an empty input field"fred-import": "cta_settings"
does not work in parameter sets. You need to create the parameters again.(ERROR @ .../core/vendor/xpdo/xpdo/src/xPDO/xPDO.php : 666) Could not load class: FredTheme from mysql.fredtheme
&emailFrom=
contact-us@[[++site_url:stripString=http:
:and:stripString=https:
:and:stripString=/
:and: stripString=www.
]]``p.s. The first two bugs are the most critical of all. If necessary, I can provide private access to the environment where the bugs described above exist.
The text was updated successfully, but these errors were encountered: