-
Posts
9 -
Joined
-
Last visited
Posts posted by halima
-
-
Why you talking so much about context?
The only purpose for me to cache before first load is provide faster page loading for guests (they are the most part of site visitors).That's very important if you need to update site content many times a day (for example at news sites).I thought ProCache has such feachure, but it doesn't. So i have to work hard on crontab tasks that will crawl entire site every minute to make page load fast for EVERY user.
Why you talking about resources in times when hardware becomes cheaper every day?
User experience is more valuable than resources.
The last thing: why should i care about cache expiration? It should be updated ("expired") only if it's content is changed (and then cached again).
-
If you are determining language from the hostname (i.e. en.domain.com, it.domain.com, etc.), then you'd have to have a before(Page::render) hook that sets the $user->language based on the hostname.
Hello.
I'm trying to implement language switching by using GET-parameter. Can you help me to understand how hook works?
if ( $_GET['lang'] == 'en'){ wire()->addHookBefore('Page::render', function($event){ $user->language = $languages->get("en"); $user->save(); }); }
What am I doing wrong?
-
It seems processwire missed ProcessProfile module
I've installed it in module manager and LanguageSupport install error disappeared
-
Hello, guys.
I've just updated processwire to 2.6.6 dev and i get the same error when trying to install LanguageSupport module
What's the problem? How to fix it? I could provide any information that helps. Any ideas?
-
I'm no expert with language support or module creation, however it would seem that you need to install LanguageSupport module before installing ProcessLanguage or ProcessLanguageTranslator.
I got these errors when i'm trying ti install LanguageSupport module
Any reason why you'd use this version? There where a lot of different fixes leading up to 2.6.0 so you should really be using it if you want a stable installation.
Thank you, i will try to update and report about results.
-
Hi,
I've just entered Invalid value sent to Page::setTemplate in Google and have found several links, starting from the first ones, pointing to ProcessWire Topics/Posts in these Forums or to the ProcessWire GitHub.
Some are related to the repeater field(s).
They seem to give good clues/solutions.
Hope that helps.
By the way, which version(s) are you both using?
i'm on 2.5.25 dev and still cannot find a solution
-
Hello.
I've just installed clean ProcessWire 2.5.25 dev
When i'm trying to install LanguageSupport i get this error:
No module specified Module Install - Installed ProcessLanguage Created fieldgroup: language (107) Created field: language_files_site Created field: language_files Created Template: language Created Default Language Page: /pwadmin/setup/languages/default/ Installed ProcessLanguageTranslator Created Language Translator Page: /pwadmin/setup/language-translator/ Created Langage Field: language Unable to install module 'LanguageSupport': Unable to find ID for Module 'ProcessProfile' Failed module dependency: ProcessLanguage requires LanguageSupport Failed module dependency: ProcessLanguageTranslator requires LanguageSupport
Why it happened? How should I install LanguageSupport?
-
I've got literally the same issue
Anybody knows why?
Why not pre-cache on save, instead of on request? (possible?)
in General Support
Posted
Thank you guys for your answers. I didn't want to be rough.
Let's imagine that you have:
If you'll update just one page (article) it would affect all other connected pages. That's rather more than just one user issue.
Captain Earth: Saving a page is not a problem, because it happens not so often and doesn't affect guest users (who is the most part of audience)
Hero Member: It's more simplier for me to tell editor do not save page too fast than ask him to crawl all over pages affected by one edited article. I don't understand why are you talking about free tool, because i needed to buy ProCache for using it.
Sorry, i didn't notice that it is not ProCache thread.