@arc002 ajaxify.data is just the data the template was run with. Changing it does nothing to the already rendered page.
What you want is to add a hook for filter:topics.getand modify the data there.
I've added a domain (alias) to Openshift to my app name so I don't have to do namespace-domain.rhcloud.com, but whenever I use the domain NodeBB doesn't work. For example I cant make changes in the Admin CP or delete/lock/pin any topics. But when I go to namespace-domain.rhcloud.com, everything works fine. Do I have to change the NodeBB setup domain name ?
@Aureney Yes, you need to change the
url field in your
config.json file to the url of your domain.
@PitaJ Uh.. how do I do that? Do I edit the file in my local repo and do git push origin master again?
@Aureney I don't know what your personal setup is, but you need to somehow change that file and restart NodeBB.
@PitaJ where exactly is config.json? I can't find it in the nodebb files
@Aureney it's created by the setup utility in the root directory of NodeBB.
@PitaJ It's not in the root directory?
@Aureney if you ran setup, it should be there right next to
@Aureney you should have a config.json file at least on your server. Try sshing in and changing it there.
@PitaJ I'm newbie at SSH. What do I do?
@Aureney I'm not gonna explain it to you: Google is helpful for that. There should be a tutorial for whatever your setup is.
@PitaJ No luck. All there is is just
./nodebb setup but it doesn't work on Openshift for some reason.
Actually the guide you use overwrites the NodeBB config within its startup-script.
It uses the
OPENSHIFT_APP_DNS_ALIAS and fallback
OPENSHIFT_APP_DNS environment variables. So I guess those should be set by openshift and only a restart of NodeBB would be necessary.
You are using a custom script, thus that scripts author/support is the correct person to ask for troubles.
You seem to already have started a discussion at GitHub, reference: https://github.com/ahwayakchih/openshift-nodebb/issues/20
Next time, please provide more information within OP; Could've saved @PitaJ some time.
@frissdiegurke I know. That's why I started it.