Skip to content

[4.0] Fixed problem with "progressive cache"-option#26262

Closed
Schmidie64 wants to merge 4 commits intojoomla:4.0-devfrom
Schmidie64:j4_fix_cache_progressive_error
Closed

[4.0] Fixed problem with "progressive cache"-option#26262
Schmidie64 wants to merge 4 commits intojoomla:4.0-devfrom
Schmidie64:j4_fix_cache_progressive_error

Conversation

@Schmidie64
Copy link
Copy Markdown
Contributor

Summary of Changes

Fixed a problem, in the global configuration->system-tab->System Cache Option.
If "ON - Progressive caching" ist selected and you try to open the frontend, you get an error
error_cache

Testing Instructions

  1. Go into your websites backend

  2. Go to the Global Configuration

  3. Go to the system tag

  4. Set the System Cache to "ON-Progressive Caching"

  5. Go tot your sites frontend

  6. Now you shout get an error-message

  7. Now apply my patch and redo the Testing Instructions

@ghost ghost changed the title Fixed problem with "progressive cache"-option [4.0] Fixed problem with "progressive cache"-option Sep 11, 2019
{
$cache = CmsFactory::getCache('com_modules', '');
$hash = md5(serialize(array($name, $attribs, null, $renderer)));
$hash = md5(serialize(array($name, $attribs, null, json_encode($renderer))));
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we not just use the class name of the renderer instead of encoding the whole class? Would speed up things a bit or do we need to take here into account the whole object?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@laoneo If we just take the name, the hash would be different if the content of the renderer differs even though the name is the same I guess. If we just take the name, the hash would always be the same even if the content of the renderer is different.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that true? None of our renderers implement JsonSerializable as an interface. Sadly if i run

json_encode($renderer) and dump that out i currently get

<PathToCMS>/libraries/src/Document/HtmlDocument.php:470:string '{}' (length=2)

@ahghatol
Copy link
Copy Markdown

ahghatol commented Oct 19, 2019

I have tested this item ✅ successfully on 94a8776

@KishoriBKarale
Copy link
Copy Markdown

I have tested this item ✅ successfully on 94a8776


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@Neppert
Copy link
Copy Markdown

Neppert commented Oct 19, 2019

I have tested this item ✅ successfully on 01dae5d

Did conflict with the activated patch 19416 (countModules) - an issue with the library.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@crommie
Copy link
Copy Markdown

crommie commented Oct 19, 2019

I have tested this item ✅ successfully on 01dae5d

Works!


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@ttplpoojak
Copy link
Copy Markdown

I have tested this item ✅ successfully on 01dae5d


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

1 similar comment
@ttplpoojak
Copy link
Copy Markdown

I have tested this item ✅ successfully on 01dae5d


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@Neppert
Copy link
Copy Markdown

Neppert commented Oct 19, 2019

Later I got problems to show menu items. So check the table: ##_contentitem_tag_map' doesn't exist


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@alikon
Copy link
Copy Markdown
Contributor

alikon commented Oct 20, 2019

RTC


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@joomla-cms-bot joomla-cms-bot added the RTC This Pull Request is Ready To Commit label Oct 20, 2019
@atpatil11
Copy link
Copy Markdown

I have tested this item ✅ successfully on 01dae5d

I've tested this patch. It works!

Thanks for detailed testing instructions :)


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@pravinTek
Copy link
Copy Markdown

I have tested this item ✅ successfully on 01dae5d


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/26262.

@wilsonge
Copy link
Copy Markdown
Contributor

wilsonge commented Nov 3, 2019

Whilst this stops the fatal the patch is clearly wrong per Allon's comment as all that is resolved is an empty json string :(

@Quy Quy added the Updates Requested Indicates that this pull request needs an update from the author and should not be tested. label Nov 3, 2019
@wilsonge
Copy link
Copy Markdown
Contributor

wilsonge commented Nov 5, 2019

Closing in favour of #27000

@wilsonge wilsonge closed this Nov 5, 2019
@joomla-cms-bot joomla-cms-bot removed the RTC This Pull Request is Ready To Commit label Nov 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Updates Requested Indicates that this pull request needs an update from the author and should not be tested.

Projects

None yet

Development

Successfully merging this pull request may close these issues.