Johnny...
Version control, my friend, version control.
Stop everything you are doing, right now, and adopt a version control
system.
You could use Git, or you could use Mercurial. Either one is fine. Git is
far more popular - you may want to pick it for that reason. But Mercurial
is also very nice and can be easier to understand.
You can even try both and see which you like. Either way, don't use the Git
or Mercurial command line. Use one of the GUI clients that are available
for both. My favorite is SmartGit (which also works with Mercurial). But it
is a bit complex to get started with, because it offers so many features.
You might try starting with GitHub's desktop Git client (even if you don't
use Git), or TortoiseHg if you find you like Mercurial. SourceTree is also
very nice. (And don't overlook SmartGit; it's not *that* difficult, just is
so feature-filled that it looks complicated at first.)
Once you create a Git or Mercurial repository, you can use it with any
client, or with the command line, so you won't be locked into SmartGit or
SourceTree or the GitHub client.
Start with a practice project. Create a skeleton HTML page or PHP file,
with almost nothing in it. Commit that. ("Committing" means creating a new
revision in the version control system.) Make a little change and test it.
Commit that change. Another little change. Commit it. Add a script. Commit
that. Add a feature. Commit that. Try a little refactoring: rename a
function or something. Commit that too.
Are you getting the idea? Commit, and commit, and commit again, after every
little change.
Every one of your commits goes into your version history, and you can go
back to any of them at any time. Once you commit a change to the version
control system, you never have to worry about losing it!
If you mess things up, you can even commit your messed-up version - and
then you can go back to an earlier version, or an earlier one than that, to
get back to a state where things worked. You can go back and forth between
the old working code and newer broken code, and see exactly when and how
things broke. The more often you commit your changes, the easier it is to
do this.
Of course, none of this will help with your current situation where the
code is broken and you're not sure what changes caused the problem. But you
will never have to have this happen again.
Do this. Do it now. It will be like gaining a superpower.
On Mon, Oct 19, 2015 at 4:25 PM, johnnypemail <johnnypem...@gmail.com>
wrote:
> This is a custom google javascript api where address are loaded from
> database.
>
> The map was working great.. I started adding other functionalities to the
> site... lost track and now the map is not showing up .. please help! :(
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google Maps JavaScript API v3" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-maps-js-api-v3+unsubscr...@googlegroups.com.
> To post to this group, send email to
> google-maps-js-api-v3@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-maps-js-api-v3.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-maps-js-api-v3+unsubscr...@googlegroups.com.
To post to this group, send email to google-maps-js-api-v3@googlegroups.com.
Visit this group at http://groups.google.com/group/google-maps-js-api-v3.
For more options, visit https://groups.google.com/d/optout.
