Hi.
I seem to be having problems when trying to edit members notifications screen

It loads but when you try and click the forum topic activity box the following error shows

An error has occurred
An error occurred when loading this screen onto the web browser. You are being notified of this as you are staff. If you believe this is a bug in Composr, please contact the developers with full details. More details are available in your browser's error console. The error was:

1: Uncaught ReferenceError: handle_notification_type_tick is not defined
http://<domain>/index.php?page=members&type=view&id=<xxx>#tab__edit__notifications

Thereafter the notification screen locks.

I have tried clearing the template cache but no difference

Is this all browsers or a specific browser?
It looks like the notifications JavaScript file isn't loaded.

I just tried to reproduce on Chrome and Firefox, and all was normal. The notifications.js script is loaded up via the AJAX response when clicking on the edit tab.

I wonder if maybe you have some browser addon filtering out scripts (e.g. an ad blocker), or an exotic web browser, or an old version.

Try rebuilding your cache

Hi,
A Little bit more information.
I can reproduce this every time on my Samsung S7 edge mobile using either Google chrome, or Samsung internet browser, or Firefox, in both Mobile or Desktop mode, but Firefox on my mobile has reported the error slightly differently :

1: Uncaught ReferenceError: handle_notification_type_tick is not defined
http://&lt;domain&gt;/themes/FuchsFriends_UK/templates_cached/EN/global_mobile.js?1500066964
line 729 > eval

So the except from this file is :

function inner_html_copy(dom_node,xml_doc,level,script_tag_dependencies){if(typeof level=='undefined')level=1;if(level>1){var node_upper=xml_doc.nodeName.toUpperCase();if((node_upper=='SCRIPT')&&(!xml_doc.getAttribute('src')))
{var text=(xml_doc.nodeValue?xml_doc.nodeValue:(xml_doc.textContent?xml_doc.textContent:(xml_doc.text?xml_doc.text:'')));if(script_tag_dependencies['to_load'].length==0)
{window.setTimeout(function(){if(typeof window.execScript!='undefined')
{window.execScript(text);}else
{eval.call(window,text);}},0);}else
{script_tag_dependencies['to_run'].push(text);}
return;}
if(xml_doc.nodeType==1){var this_node=dom_node.ownerDocument.createElement(xml_doc.nodeName);for(var a=0,attr=xml_doc.attributes.length;a<attr;a++){var a_name=xml_doc.attributes[a].name,a_value=xml_doc.attributes[a].value,evt=(a_name.substr(0,2)=='on');if(!evt){switch(a_name){case'class':this_node.className=a_value;break;case'for':this_node.htmlFor=a_value;break;default:try{this_node.setAttribute(a_name,a_value);}
catch(e){};break;}}else
{try{this_node[a_name]=eval('var x=function(event) { '+a_value+' }; x;');}
catch(e){};}}

And Line 729 is the bolded text.

I agree that on my PC this functionality all seems to work without any problems, and in all other respects the website works absolutely fine on my S7 mobile in chrome.

So I have cleared the Caches, re-started the apache server, but sadly on my mobile the problem exists. Odd.

Is there any other debugging I can enable to would help you ?

Website address?

Hi Paul.
As this is a members only site if you want to PM me then i can provide you the url and give you a temporary membership if thats what you need
Chris

Hi,

Please try this sources/cns_profiles.php file:

https://raw.githubusercontent.com/ocproducts/composr/ef8bcbffab699b2de229f9e4d1f164b58d128a1c/sources/cns_profiles.php

I couldn't reproduce the issue, but I think something else is going on and this simplifies how it works.

Hi Chris,
Sorry for the late reply, summer hols etc.
Thanks for the suggested patch, but unfortunately it did not make any difference.
Its clearly something specific on my installation, as my phone browser works without any problems on my profile your compo.sr members area.

Thanks anyway.

Hi,

(For anyone reading, I was provided access)

This should now be fixed.
There was a performance issue on JavaScript compilation that triggered a timeout on your particular server. For my phone it was actually hanging the page rather than showing an error message. I was able to optimise the code, so this is a nice improvement for everyone.

I also found some mobile layout issues I fixed when testing.

I also updated your theme's global.css, as there had been fixes to the default since you created your theme.

Hi chris,
Many thanks, it's now working on my mobile without problems.

Your support is once again really appreciated.
Chris

Automated fix message

Chris Graham said

Here's the tracker issue we have:
0000390: Data laws - Composr CMS feature tracker

This issue has now been filed on the tracker as issue #5369, with a fix.