hiy0104
Active member
That's a pretty dick move. I'm out here purchasing modules to give updates and you're trying to bargain for a trade lol. Just post the Combo Twitter module.
Yes, social networks are very quick to ban accounts using obvious shared proxies. Be smart about it, if your client / account is located in Canada, obviously get a residential or mobile proxy from Canada. And make sure it's not a rotating proxy. Safest way for me was to create a proxy client on my phone using Termux then set up a reverse proxy server on my VPS. When using automation, it looks like it's coming from my phone. Like so:
Good luck.
======================
To everyone having difficulties with installation, make sure to read the OFFICIAL docs at the stackposts website. I'm a developer and even I had difficulties with some things here and there, so this is definitely not an "easy" script to set up. I've had to fix the Stripe payment bug on my own without the official update, I've had to make some changes to the core CI files, etc.
The best way to get help is to explain in DETAIL what the problem is, how you got there, what you see, what page you are on, etc.
But first, make sure:
1) The files listed in the installation docs are ACTUALLY writeable. On one occasion, The installer showed mine as writeable, cause the CHMOD permissions were correctly set. However, the OWNER of the files were set to root because I uploaded the files through a root account. Make sure the entire directory of the whole app (not only the writeable ones) are owned is set to www-data:www-data (www-data user belonging to www-data group), or add the current owner to the www-data group.
2) In the console (press F12 on chrome), if you ever get a Javascript error for an undefined function, try deleting the cache file in the /app/ or /assets/ folder, forgot which (named core.js).
3) If your having multiple problems, edit your index.php file in the home directory. On line 2, change it to
Code:
define( 'ENVIRONMENT' , 'development' );4) Make sure your apache settings are set correctly, obviously.
5) I'm sorry I can't help every one here individually, I'm a pretty busy guy. Try to debug it yourself, if the installation succeeded and something is not working afterwards, then it's your server and/or your configurations. Look at your php logs, apache logs, turn CI's error logging on (it's off by default, as thats how the developer released it), browser console (tells a lot once you set it to development mode), and try to learn. Google is your friend.
6) If you must ask for post-installation help here, be as detailed as possible: What error did you get, what were you trying to do when you got the error, what's outputted in console, etc.
