This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 9:00 – 14:00 | 9:00 – 14:00 | 9:00 – 14:00 | 9:00 – 14:00 | 9:00 – 14:00 | - |
- | 15:00 – 18:00 | 15:00 – 18:00 | 15:00 – 18:00 | 15:00 – 18:00 | 15:00 – 18:00 | - |
Supporter timezone: Asia/Dhaka (GMT+06:00)
Tagged: Bug
This topic contains 43 replies, has 2 voices.
Last updated by Prosenjit Barman 7 months, 2 weeks ago.
Assisted by: Prosenjit Barman.
Author | Posts |
---|---|
August 27, 2024 at 4:47 am #16107238 | |
peterB-149 |
Please provide an update. |
August 28, 2024 at 3:43 am #16112374 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi There! We checked and found that some CSS rule wasn't properly applied to the MD version of the site, causing an element below the menu item to appear incorrectly on the frontend and other styling issues. This issue may have occurred due to the optimization of the CSS files. I added the CSS rules specifically for the MD version under "Appearance > Customize > Additional CSS", then cleared the used CSS and caches from WP Rocket. After these changes, the header on the MD version now displays correctly on Desktop and Mobile. I monitored the site for an hour and can confirm that the styling issue is not happening now. Please clear the caches on your site and browser, or view the site in incognito mode. The layout should appear correctly. Thank you for your patience and cooperation. If you need any further assistance, please don't hesitate to reach out. I'll be happy to help. Best regards, |
August 29, 2024 at 8:32 am #16118381 | |
peterB-149 |
I have just checked the MD site and it is still not fixed? |
August 29, 2024 at 8:36 am #16118471 | |
peterB-149 |
Surely this is an issue with site translation? The original language site (IN) and the EE site which is a translation work perfectly fine however the MD site does not. Something must not be carrying over to this site? Can we please prioritise getting this fixed as I have now been waiting over a month with a broken site and have lost revenue as a consequence. |
August 29, 2024 at 3:54 pm #16121115 | |
peterB-149 |
You have once again published publicly my site details. This has happened several times, please do not do this and make these images private. I test properly every single time you tell me that it is fixed using incognito mode. I have just checked and the problem is still not fixed. |
September 2, 2024 at 3:59 am #16129833 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi There, I'm very sorry for the inconvenience. As soon as I noticed that the image displayed site information, I made that response private. We respect your site's privacy and will ensure that any future responses containing information about your site are kept private. I have a solution in place, but it periodically stops working, which seems to be related to caching issues. I've reached out to our second-tier team for a deeper analysis, and they are going to take another closer look. As soon as I have any information on that, I will surely inform you. Please note that I've increased its priority in our internal ticketing system. Thank you so much for your patience and kind cooperation in this matter. Best regards, |
September 2, 2024 at 9:22 am #16130713 | |
peterB-149 |
Hi, As I have stated before there must be a problem with the translation of the MD site as the EE site works perfectly and that is a translation. I'm not talking about translated pages, there is obviously some problem with how the cache settings or something similar is being translated from IN to MD domains? I opened this ticket on the 24th July and we are now in September, can we please work to get this resolved today? Adding exclusion rules for CSS files in the settings is not the long term solution as I am planning to add many more tlds to this site, I am just waiting for the fix for this. Regards, |
September 3, 2024 at 4:11 am #16133826 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi Peter, Thank you for your patience and understanding as we continue to address the issue you're experiencing with the MD and LU domains. I completely understand your concerns, especially given the time this has taken. As you know, we have explored and implemented several solutions that initially seemed to resolve the issue. However, due to caching or file optimization, these solutions have unfortunately stopped working on the LU and MD domains. It's clear that there is a deeper issue with the caching settings specific to the MD and LU domains that need to be addressed to ensure a lasting fix. Our 2nd tier team is actively investigating this, and I have shared all the necessary information with them to help expedite the process. The challenge lies in the irregular nature of the issue, which only becomes apparent after some time, complicating our efforts to trace and resolve it quickly. Please rest assured that we are fully committed to finding a permanent solution. While I cannot provide a precise timeline at this moment, we are doing everything possible to resolve this as soon as we can. I will keep you updated with any new developments from our team. I sincerely apologize for the inconvenience this has caused, and I deeply appreciate your cooperation and understanding. We are dedicated to ensuring that your site functions seamlessly across all domains, now and in the future. Thank you again for your patience. Best regards, |
September 3, 2024 at 9:37 am #16134765 | |
peterB-149 |
Can I please get an ETA on this fix? |
September 4, 2024 at 4:30 am #16138254 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi Peter, The issue is currently being investigated by one of our developers, and they have traced the problem to how WP Rocket is loading CSS files on the MD version of the frontend. They also noticed interference from the following script: - hidden link Reaching a permanent fix may take some time, as the issue only occurs after several hours. Once a fix is implemented, we will need to monitor it for a few hours to ensure the problem does not reoccur. If everything remains stable, we will inform you that the issue has been resolved. At this time, I don’t have a solid ETA on when the fix will be completed, but please know that it’s a top priority, and we are working actively to resolve the issue. Thank you for your patience and cooperation in this matter. In the meantime, if you notice anything or have any information that might help speed up the process, please feel free to share. We’ll be happy to assist further. Best regards, |
September 9, 2024 at 5:39 am #16153448 | |
peterB-149 |
Hi, please provide an update. |
September 10, 2024 at 7:41 am #16159725 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi Peter, Thank you for your continued patience and collaboration as we worked through the issue. After conducting a thorough investigation and testing, our developers have identified that the issue was related to how WP Rocket handled CSS optimization. The CSS optimization method has been set to “Load CSS Asynchronously”, and after monitoring for a full day, we can confirm that the layout issue is no longer occurring. The layout across all languages, including the Romanian version, is now displaying correctly. I'm including the Key Findings from the developer below: Next Steps and Recommendations: If the issue reappears on the Romanian domain (`example.md`), we recommend reaching out directly to WP Rocket’s support team for more specialized assistance. They may be able to offer more detailed guidance on resolving the issue, particularly if the optimization feature has any dependencies related to the domain or language setup. Feel free to share the steps we’ve already taken with them, and they’ll be able to continue troubleshooting from where we’ve left off, using their own methods to resolve the issue. Alternatively, you can hire a contractor from our trusted contractor list for prompt help. Thank you once again for your trust in our work, and we’re always here to help if you need anything else. Best regards, |
September 10, 2024 at 9:10 am #16160103 | |
peterB-149 |
Thank you, but can you please confirm why the IN and EE domains were working perfectly with CSS optimization set to "Remove Unused CSS"? WP Rocket doesn't have individual settings for domains in a WPML set up, the settings should be carried accross to each domain which is handled by WPML. |
September 11, 2024 at 3:27 pm #16167189 | |
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hello There, You're absolutely right that in a multidomain environment, WPML applies the settings to each domain. However, since caching is handled by WPRocket, there may be something in their code that didn’t work properly for the Romanian language or due to the unique locale you used for Romanian (ro-md). I hope the WPRocket team can provide more insight into this issue. I can now see that the CSS on the Romanian version of the site is consistently displaying correctly. I haven't noticed any differences since yesterday. It seems the issue has been resolved after adjusting the caching settings and changing the language URL format. If you have any other questions, feel free to let me know. I will be happy to help. Best regards, |
The topic ‘[Closed] CSS files not loading on translated version of website’ is closed to new replies.