CSS3 Buttons [support thread]

[DivaVocals]

You can also do "interesting" things like:

define ('CSS_BUTTON_POPUPS_IS_ARRAY', 'true');
define ('CSSBUTTONS_CATALOG_POPUPS_SHOW_BUTTON_NAMES_TEXT', ': No title defined; see ' . __FILE__);
$css_button_text = array ();
switch ($current_page_base) {
  case FILENAME_ACCOUNT_EDIT:
  case FILENAME_ACCOUNT_HISTORY:
  case FILENAME_ACCOUNT_NEWSLETTERS:
  case FILENAME_ACCOUNT_NOTIFICATIONS:
  case FILENAME_ACCOUNT_PASSWORD:
    $css_button_text['button_back'] = 'Return to <em>Manage Your Account</em>';
    break;
  default:
    if (strpos ($current_page_base, FILENAME_ADDRESS_BOOK_PROCESS) !== false) $css_button_text['button_back'] = 'Return to your <em>Address Book</em>';
    else $css_button_text['button_back'] = 'Return to the previous page';
    break;
}

That is, you can customize the buttons' title text based on the page context.

Nice.. I'm sure I'll break some ish doing this.. One question.. this example covers the back button.. Can I do the this without blowing something up??

define ('CSS_BUTTON_POPUPS_IS_ARRAY', 'true');
define ('CSSBUTTONS_CATALOG_POPUPS_SHOW_BUTTON_NAMES_TEXT', ': No title defined; see ' . __FILE__);
$css_button_text = array ();
switch ($current_page_base) {
  case FILENAME_ACCOUNT_EDIT:
  case FILENAME_ACCOUNT_HISTORY:
  case FILENAME_ACCOUNT_NEWSLETTERS:
  case FILENAME_ACCOUNT_NOTIFICATIONS:
  case FILENAME_ACCOUNT_PASSWORD:
    $css_button_text['button_back'] = 'Return to <em>Manage Your Account</em>';
    break;
  default:
    if (strpos ($current_page_base, FILENAME_ADDRESS_BOOK_PROCESS) !== false) $css_button_text['button_back'] = 'Return to your <em>Address Book</em>';
    else $css_button_text['button_back'] = 'Return to the previous page';
    break;
switch ($current_page_base) {
  case FILENAME_ACCOUNT_EDIT:
  case FILENAME_ACCOUNT_HISTORY:
  case FILENAME_ACCOUNT_NEWSLETTERS:
  case FILENAME_ACCOUNT_NOTIFICATIONS:
  case FILENAME_ACCOUNT_PASSWORD:
    $css_button_text['button_forward'] = 'Return to <em>Manage Your Account</em>';
    break;
  default:
    if (strpos ($current_page_base, FILENAME_ADDRESS_BOOK_PROCESS) !== false) $css_button_text['button_forward'] = 'Return to your <em>Address Book</em>';
    else $css_button_text['button_forward'] = 'Return to the previous page';
    break;
}

[lat9]

I've had sites where I've organized this file by alphabetical button-name (as indicated in your example, above) and other sites where it made more sense to organize the file by page, as below. It all depends on which way you (or whoever is going to maintain the list) find it easier to locate/verify that all the title-text values are supplied.

define ('CSS_BUTTON_POPUPS_IS_ARRAY', 'true');
define ('CSSBUTTONS_CATALOG_POPUPS_SHOW_BUTTON_NAMES_TEXT', ': No title defined; see ' . __FILE__);
$css_button_text = array ();
switch ($current_page_base) {
  case FILENAME_ACCOUNT_EDIT:
  case FILENAME_ACCOUNT_HISTORY:
  case FILENAME_ACCOUNT_NEWSLETTERS:
  case FILENAME_ACCOUNT_NOTIFICATIONS:
  case FILENAME_ACCOUNT_PASSWORD:
    $css_button_text['button_back'] = 'Return to <em>Manage Your Account</em>';
    $css_button_text['button_forward'] = 'Go somewhere else';
    break;
  case FILENAME_ADDRESS_BOOK_PROCESS:
    $css_button_text['button_back'] = 'Return to your <em>Address Book</em>';
    break;
  default:
    $css_button_text['button_back'] = 'Return to the previous page';
    $css_button_text['button_forward'] = 'Go to the next page';
    break;
}

[DivaVocals]

I've had sites where I've organized this file by alphabetical button-name (as indicated in your example, above) and other sites where it made more sense to organize the file by page, as below. It all depends on which way you (or whoever is going to maintain the list) find it easier to locate/verify that all the title-text values are supplied.

define ('CSS_BUTTON_POPUPS_IS_ARRAY', 'true');
define ('CSSBUTTONS_CATALOG_POPUPS_SHOW_BUTTON_NAMES_TEXT', ': No title defined; see ' . __FILE__);
$css_button_text = array ();
switch ($current_page_base) {
  case FILENAME_ACCOUNT_EDIT:
  case FILENAME_ACCOUNT_HISTORY:
  case FILENAME_ACCOUNT_NEWSLETTERS:
  case FILENAME_ACCOUNT_NOTIFICATIONS:
  case FILENAME_ACCOUNT_PASSWORD:
    $css_button_text['button_back'] = 'Return to <em>Manage Your Account</em>';
    $css_button_text['button_forward'] = 'Go somewhere else';
    break;
  case FILENAME_ADDRESS_BOOK_PROCESS:
    $css_button_text['button_back'] = 'Return to your <em>Address Book</em>';
    break;
  default:
    $css_button_text['button_back'] = 'Return to the previous page';
    $css_button_text['button_forward'] = 'Go to the next page';
    break;
}

Okay.. I'm gonna play..

SLIGHT off topic (but kinda related) question:
Is there similar code for the admin CSS buttons???

[lat9]

Okay.. I'm gonna play..

SLIGHT off topic (but kinda related) question:
Is there similar code for the admin CSS buttons???

Kinda-sorta-not-exactly-related answer: Nope

[DivaVocals]

Kinda-sorta-not-exactly-related answer: Nope

okay.. will ask more details in the right support thread..

[remops]

Something has happen and now the "checkout" button and the "continued shopping" button on the shopping cart page are just links. Some of the other css buttons formatting has also changed.

The website is http://www.tissue-box-covers.com/

The Checkout and continue shopping looks to be links but I am sure that I had these set as css buttons.

I haven't checked this shopping cart page for some time and maybe I am just confused that it was a button

Thanks

[remops]

OK I found that adding the mobile template by AlgoZone changed the css settings.

Thanks to Mike at Geekhost this has been fixed.