Someone could spend a DB base? is that when I install, I get that I can not, because the DB is not supported.
Thanks
i got a vps for u ready 100% secure and for free becouse i dont use my vps anymore becouse i got now a dedi but my contract of my vps still runs till next year so u may use it if u dont edit my personal data on it
it got the following services on it
Mysql database
Ftp account
website
Remote desktop
u can make a new db so non of my old db has to be removed if i can trust u 100 % we dont need to argu about my details on that vps ;)
For VPS Details ask me in a pm
greetings,
Angelokreikamp
SVN users: http://code.google.com/p/phpretro/source/detail?r=68
New revision now updates SSO ticket on every client.php load.
New captcha system. The old one (as with HoloCMS) is crackable (I may make a attack tool one day). This one is more secure as it distorts and turns the image.
I still have the same problem.
URL problem: http://mysite/client_error?error=loa...lient_uptime=0
Look:![]()
Also, Yifan. When I was using PHP retro, Users were having trouble registering successfully. After filling out their details and entering the capatcha and clickinf submit, the registration form would hang for a long long time and then sometimes their details may have not been submitted to CMS_users or just the users table.
Thich is quite a large bug, as what happens then is that they cannot re-register with the same name (and cannot access the CMS properly) - Without me deleting the SQL area, which would mean further bugs, etc.
Support:
If you have any problems, add yifanlu (at) phpretro.com to your MSN and I'll try to help you with whatever problem you're having. Please beware that I'm very impatient, so prepare for me to insult you if you ask something that I've answered already.
Please still try to submit bugs to Google Codes. Contact me directly and I'll try to find out and/or fix the problem one on one. It's really hard to differentiate between actual bugs vs. noobs who can't follow directions, so I'm hoping this will allow better bug-fixing.
Last edited by yifan_lu; 07-08-09 at 03:00 PM.
I need help in setting up smtp email server so i can test out the forgot password and the verify email.
yifan_lu, the problem of tick_sso already solved? The error remains for me
@pedro ferraz can you read? If so, read my last post.
I got This Problem I Installed Php Retro I Followed The New Tutorial And It Still DOnt Work I Cant Login It Takes Me To Error Page And I Cant Register Because It Doesnt Check If NAme Is IN Use Or NOt. Can Anyone Help![]()
@yifan_lu the new revision the sso thing to generate sso ticket when client opens doesnt work for me i get the same error as i did before and when i log off the cms and log back in then load client it works still
EDIT:
hmm vB seems to show me nederlanders post at the bottom what's up with that.
[ontopic]
Yifan have you considered including say a DB update script with each release.
In 4.0.2 b3 you included a check in the installer to see if hc_before was present in the db and if it wasn't you created it.
Might it not be a good idea to include these DB changes in an upgrade script that people run with with each new version?
Yes, they could (and I did) create the field manually, but I suspect that some may have just copied over the old files thinking that would have solved the bug, not realising that they would need to either manually create the field or re-run a fresh install.
Last edited by lambada; 07-08-09 at 07:28 PM.
Oops, if you added me via MSN, add me again. I accidentally pressed Ignore All.
Hey sisija, Jusy wondering if you needed a Vps? If you do please pm me f not dis-regard this post, thanks Lee.
Yes but when i'm logged in and I restart the server, the server sets SSO tickets to NULL ;)
Maybe a good idea from tomspit to generate a ticket when opens te client
huh?
I post it a few posts before
http://code.google.com/p/phpretro/source/detail?r=69
New revision!
-Added Groups deleting (oops, missed it first time around)
-Fixed group badges not saving (thanks for the report, I know there's still
more)
-Fixed groups purchasing on new installation, old installations, please run this
query-Added new captcha (forgot last commit)Code:ALTER TABLE `groups_details` CHANGE COLUMN `description` `description` text CHARACTER SET utf8 NOT NULL, CHANGE COLUMN `type` `type` tinyint(1) NOT NULL DEFAULT '0', ADD COLUMN `forumtype` tinyint(1) NOT NULL, ADD COLUMN `forumpremission` tinyint(1) NOT NULL, CHANGE COLUMN `views` `views` int(15) NOT NULL, ADD COLUMN `alias` varchar(30) NOT NULL, DROP PRIMARY KEY, ADD PRIMARY KEY (`id`, `alias`);
-Modified client to use new loader again (after finding it was not the problem)
I still have problems ...
PS: In another Client.php it works, more makes no automatic updates. help-me
Url error in client: http://mysite/client_error?error=loa...lient_uptime=0
Enter on MSN. yifan
This is very good. Thankyou :)
The housekeeping is missing a few pages
hey yifan_lu, why am I still having problems with the Client.php? I can not access the hotel. help me
Hey I Need Help Idk Why Its Not Working I Cant Login On The Website It Takes Me To Error Page.
Revision 70 committed: http://code.google.com/p/phpretro/source/detail?r=70
This revision mainly focused on the installer. Since I figured out that most people don't READ before trying to install. I added some checks that checks if your server supports PHPRetro before attempting to install it. I also fixed the bug where it says you don't have a valid Holograph database when you do (mainly on TDbP edition). Also, the config.php is now generated in ./install/ instead of ./includes/ and the user (you) have to manually move it to ./includes/ when install is finished. This is similar to how you install MediaWiki. Why? Because on Unix based servers, ./includes/ has premission of 755 which doesn't allow any writing. You have to make ./includes/ 777 in order for it to work. This is bad because anyone can now write to the ./includes/ folder if you forget to change it back. To make it easier and more secure, config.php is now generated in ./install/ which is CHMOD 777 and will be deleted after installation anyways. Finally, I removed the email log feature. It was pointless because it only logs when a email is sent, now IF it was sent successfully.
Basically, it's now easier, as you don't have to CHMOD 777 a bunch of things. Just 777 ./cache/ and ./install/ and you'll be ok.