Is this something else that was left out of 3.8.5 ?
My members reported this issue to me about 20 times , i looked at the template history to see if i missed a security token when updating my modified templates and indeed i did , i added the token lines of code from the new default 3.8.5 template to my template and the issue went away . is there additional coding required to fix this ?
My members reported this issue to me about 20 times , i looked at the template history to see if i missed a security token when updating my modified templates and indeed i did , i added the token lines of code from the new default 3.8.5 template to my template and the issue went away . is there additional coding required to fix this ?
Comment