Customizing page title

[vlbrown]

Does the licensed verson give me the ability to conveniently customize the page title (e.g. change it from "EasyHPCalendar" to, say, my company name?)

Or will that be something I continue to have to do by editing a .php file?

(customization would be preferred :-)

[Brian]

You can purchase the option to remove all references to EasyPHPCalendar and NashTech, Inc. Currently it doesn't allow you to add your own name, but all branding will be removed.

[vlbrown]

But our calendar still says "EasyPHPCalendar" in the title.

Can I just edit this in the .php file?

(please add an option to customize the title!)

[Brian]

In the Setup Manager or Event Manager?

[vlbrown]

I would do it in the setup maanager. I'd add a text field option to the Display configuration, available if the license allows for such customization, to customize the "<title>" field of each page.

I think commercial users would appreciate the convenience of "branding" their calendar pages this way.

[Brian]

But, where is it showing up now?

[vlbrown]

It's in the title of the calendar viewing page ... it may be somewhere else, but this is all I've ever cared about --The <title> in demo.php.

[Brian]

Feel free to modify the demo.php file to fit your needs. :)

[vlbrown]

But I'm asking for a customization feature :-)

[Brian]

Sorry. I was under the impression from Post 3 that there was a file displaying EasyPHPCalendar when it shouldn't be. So, I was just stating that the demo.php file is meant to be edited/modified as needed.

As far as "branding" the Setup or Event Manager, this isn't something I can offer at this time. however, you are free to change the header image to anything that would fit your needs.

[vlbrown]

Sorry. I was under the impression from Post 3 that there was a file displaying EasyPHPCalendar when it shouldn't be.

Well, in my opinion, there is :-)
in my opinion, if we pay to make the "EasyPHPCalendar" display go away, that should include the <title> tags :-)

As far as "branding" the Setup or Event Manager, this isn't something I can offer at this time.

Well understood. That's why this is a feature request.

however, you are free to change the header image to anything that would fit your needs.

Interesting point. Unrelated to my posts, but thanks nonetheless.

[Brian]

There is no branding (including title tags) in the public pages when that option is purchased.

From the purchase page:

**** This option will remove all references to EasyPHPCalendar and NashTech, Inc. from all public pages and pop-ups (and includes all of the other options above) once the license key is entered. This includes the Setup Manager and Event Administration. (You'll need to update the header image with your own.) This will make both the public calendar display and the back-end setup and event management completely "brand-less".

The demo.php isn't for public display. It's for demostration purposes only so that new users can see a properly formatted page for displaying the calendar (as well as other options).

Just don't want anyone to get the wrong idea. ;)

[vlbrown]

We've definitely got "the wrong idea" because we licensed the app, my exec. assistants are merrily adding content, and the "demo.php" page is still being displayed.

What did we miss? (they found so much, whatever we missed was apparently pretty easy to miss).

The default page is (naturally) index.php. index.php runs
require("demo.php");

it doesn't get much simpler than this.

You say that
The demo.php isn't for public display.

Yet, it's being run and showing our content. I'm getting concerned that all the hard work our EAs have been putting in may get "lost". We can't have that...

What's going on?

( I know this doesn't belong in "pre-sales" questions but... where would you like to move to?)

[Brian]

The calendar isn't intended to be run from the demo page (however, it'll work fine that way), but rather, it's designed to be integrated into an existing web site. Be sure to read the integration section of the instructions so you can add the calendar to your own pages.

Also, you'll probably want to use the Setup Manager to disable the demo from being accessible from index.php (at the bottom of the main/general page). :)

[vlbrown]

it's designed to be integrated into an existing web site.

That's what index.php files are for - integrating something into an existing website. Make a link to the calendar directory et voila.

This is... unusual.

you'll probably want to use the Setup Manager to disable the demo from being accessible from index.php

Saw that. But I want index.php to be accessible :)

[ve9gra]

I still think that you don't fully get the idea of how EasyPHPCalendar works.

The files that are included in the root of the package (index.php and demo.php) are there for demonstration purposes only. The index.php can be left entirely alone as it will only display the demo if it is so enabled in the setup. Feel free to modify demo.php as much as you want, it is there only to provide a working example of how the calendar should be integrated in your own website.

Once you've confirmed that the demo is working on your server and that everything is dandy, the next step is to actually integrate it in one of your own pages, a page that follows the rest of your website's design.

Let's say your portal (home page) mostly uses top level pages to display different sections (ie: /index.php, /members.php, /departments.php, /etc.php), then it's only natural to add a /calendar.php that has the exact same look as all the other pages, but that has the required sections (read the Getting Started Guide (http://docs.easyphpcalendar.com/Getting%20Started.htm) under "Adding the Calendar to Web Pages") to display the calendar where the content goes. You can then totally modify it's appearance, changing colors, sizes, fonts, etc to match your website even further.

If you require help in acheiving this, please let us know. That's what we're here for.

[vlbrown]

I've been working with the Web since 1995.

The files that are included in the root of the package (index.php and demo.php) are there for demonstration purposes only.

The rationale behind index.php files (or index.html, index.htm, index.*) is to allow simple links to directories to cause a web page to be shown instead of a list of. files.

An index.php file should never be "for demonstration purposes only". Perhaps the contents is for demonstration purposes and expected to be edited. The file itself is a web standard.

Let's say your portal (home page) mostly uses top level pages to display different sections (ie: /index.php, /members.php, /departments.php, /etc.php), then it's only natural to add a /calendar.php

Our "portal" uses directories to display the different sections: /Facilities/, /HR/, /Communications/ -- where the index.php (or index.htm) file under the directory presents the page. it's only natural to add a /calendar/ directory and let index.php present the data

Yes, we could have a link to the calendar.php file directly. Or (as is the case with demo.php) a link to a "something.php" file that does a require of calendar/calendar.php (as is suggested in your integration notes).

But none of that is necessary because taking advantage of index.php is a very typical and consistent way to do web pages and URLs. This is why index.php was invented.

demo.php contains examples of _possibilities_ for Look&Feel. It does not use demo data. Once real data is added, "demo".php becomes "real front end".php.

For our purposes, I have renamed "demo" to a more expressive name. We like the look, thank you. If we want to play with it, we shall I have made our own, simpler, index.php.

There's more than one way to integrate a new tool into an existing site. Using an index.php file is a very common and expected way to do so.

I don't require help. But thank you for the offer. This thread should provide useful information for others.

[Brian]

Just so everyone that may read this thread understands, anyone is free to edit/modify/delete the demo.php file as well as the index.php file in the root calendar directory in any way you see fit to accommodate your needs. There is no limitation of what you can do with these files as they are there for your use.

I think the reason for the confusion in this thread is that the calendar is primarily designed to be integrated (http://dictionary.reference.com/search?q=integrated) into an existing web site (see the first paragraph on our home (http://www.easyphpcalendar.com/) page).

However, the calendar script is completely capable as a stand-alone application. And by modifying the aforementioned files, if needed, you can more accurately tailor the calendar, the page titles, layout, index page and more to your specific needs (as it seems to be the case with vlbrown).