View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0026416 | Open CASCADE | Website:Portal | public | 2015-07-10 13:45 | 2019-09-17 20:54 |
| Reporter | Assigned To | bugmaster | |||
| Priority | normal | Severity | minor | ||
| Status | closed | Resolution | fixed | ||
| Summary | 0026416: Dev portal -- Poor text hyphenation in "Active forum topics" box | ||||
| Description | "Active forum topics" box on dev portal wraps "long" lines breaking words without taking care of hyphenation rules, e.g.: * VTK integration services in O CCT * Slow Boolean Operations wit h Cylinders * Realistic 3D visualization - no t a toy anymore * Status of NIS * Removal of Persistent classe s This should be corrected by either enabling correct hyphenation, or not breaking words art all | ||||
| Steps To Reproduce | Go to OCCT dev-portal and look at the "Active forum topics" block | ||||
| Tags | No tags attached. | ||||
| Test case number | |||||
|
|
Please close as a duplicate of #26402. This was resolved. At least it works fine for me now. Clear the browser cache if it's not forking. |
|
|
Alexander, I have been able to see the fix only after I reloaded page manually. The fact is that I have just opened that page 20 min ago, thus it seems the cache may become infinitely old, and is never updated automatically, even if there are some changes on the server side. Can this be fixed somehow? |
|
|
I've just enabled CSS && JavaScript aggregation (I don't understand why it was disabled. May be there are side effects, but I have not found that effects now..) This way Drupal will give you only one aggregated CSS and JS file (+ 3rd-party JS, but it does not matter) - they will still have "infinity" expiration time. There is a button in administration page that clears all Drupal caches. This also rebuilds those JS and CSS files giving them a new random name. A browser will always download new files because they have new names. Of course, webmaster should not forget to click "Clear cache" button after he updated CSS or JS, but this is not a problem: it will be done just because it's impossible to verify the changes without this action. Moreover, cache is cleared automatically when new modules are installed or removed. I believe this will be enough. But we always have an opportunity to set expiration time for static files (e.g. the same problem might occur with pictures). Another option I'd suggest - using one modern tool: https://developers.google.com/speed/pagespeed/module/ Apart other things it will do the trick in the following way: http://stackoverflow.com/a/5588394 This job is for system team, though. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-07-10 13:45 |
|
New Issue | |
| 2015-07-10 13:45 |
|
Assigned To | => aiv |
| 2015-07-10 14:28 |
|
Note Added: 0042916 | |
| 2015-07-10 14:28 |
|
Assigned To | aiv => bugmaster |
| 2015-07-10 14:28 |
|
Status | new => resolved |
| 2015-07-10 14:28 |
|
Steps to Reproduce Updated | |
| 2015-07-10 14:56 |
|
Note Added: 0042918 | |
| 2015-07-10 16:13 |
|
Note Added: 0042924 | |
| 2019-09-17 20:54 |
|
Status | resolved => closed |
| 2019-09-17 20:54 |
|
Resolution | open => fixed |
