What about my customizations while looking at the beta?

**Website Rob** · 2 Aug 2011, 06:58 AM

Sometimes, it's easiest to just try something.

Ever tried loading: http://yoursite.com/includes/configure.php ?

**ebaobao** · 2 Aug 2011, 07:04 AM

hello website rob,
thank you for reply. i just tried that and got a nice reply, thank you. But hackers can't use any other programs besides web browser to view the file? I'm kinda new to this.

**Website Rob** · 2 Aug 2011, 07:07 AM

Discussions about hack prevention are best left to another thread.

**DrByte** · 2 Aug 2011, 07:42 AM

If a hacker has enough access to read *any* of your files the way you're worried about, then they've already got way too much access, and you have many far more serious concerns than the file permissions on your configure.php file.

And, as Rob has said, that's an entirely different topic than the one you started this thread about.

**kuroi** · 2 Aug 2011, 11:43 AM

Originally Posted by ebaobao

Hello,
What would be a good way to code and making changes so that when v1.5 is released that we don't waste all the work we have done? Thanks.

... and returning to the original question. There is no way to write code that is guaranteed to be compatible with code or changes that haven't been made yet.

The point of the beta is to allow you to give feedback on its stability and accuracy and to give you an indication of what's coming so that you can prepare for it.

Experienced developers may start to adjust their code to reflect what's there and be ready to make further tweaks as needed in response to any further changes. Or they may just plan the changes they're going to make ready for the proper release.

There will be some more code changes, but the problems that have been raised so far by the community are pretty minor and the fixes very localised. So hopefully there won't be much more to come before full release can be made.