{5} Accepted, Active Tickets by Owner (Full Description) (79 matches)

Everyone will love me for this.

I am going to grep for all app_a_... settings in Apostrophe and figure out what they are used for.

Then I will put them in app.yml either commented out or with a meaningful default value.

They will be accompanied with a comment documenting their options and purpose.

Much of Apostrophe's CSS assumes a body font size of 12px, which makes changing the font size one of the more difficult changes to make to Apostrophe's CSS. It would fantastic if more font sizes could be scaled off a configurable body font size.

Adding this ticket to keep track of this idea.

Eventually, we should open a more detailed separate tickets for events and photos if we are going to implement.

Rick, discuss with the team and then design out the flow of how this will happen and open those tickets.

We should consider making on-the-fly features in slots. 'quick add' an event to the calendar slot. Add a single image, then upload it within the slot.

I'm not sure if this is intended for the 1.1 or the 1.2 release of the blog plugin.

Right now Date just sorts ASC/DESC and I think that works fine.

In the future a dropdown should appear with the ability to choose a date or date range to filter by.

Rick create a sketch and assign to Dan

- Date search/sort is by date only. Click Published at and get a modal box with two RichDate? Widgets for selecting a range. Upon selecting the start date, the end date defaults to the same value. Optionally allowing the user to search by a range rather than day. @dan

The blog slot in particular displays messages to users when they are filtering too specifically and no blog posts are displayed.

This message is currently visible when you log out if the admin / editor doesn't relax the filters on the slot.

But really ALL slots in general should know the value of $editable in an efficient and sustainable way.

I am making this critical because it's a real bug that will affect multiple live client sites.

We should be ordering Apostrophe user admin search results to favor last names, first names, full names and finally usernames, with matches at the beginning favored over results in the middle.

You can see an example of this being implemented in the POGIL project I recently worked on. Look in /lib/filter/doctrine/sfDoctrineGuardPlugin/sfGuardUserFormFilter.class.php::addUsernameColumnQuery().

We worked through oodles of subtleties of how Doctrine does or doesn't allow custom fields and ? clauses for them, there are reasons for the PDO quote calls.

If we extend the LESS compiler to look at the project level CSS directory for a LESS file of the same name as a LESS file in the apostrophe CSS direcory.

The project level file should win, replacing the plugin level file.

This is logical and awesome and would allow us to dispense with app.yml / view.yml declarations for overriding plugin assets (when they have all been lessified)

Jake needs this asap for client work.

Laurynas Malisauskas <laurynas.malisauskas@…>

when sending mail you do not pass encoding for Zend_Mailer constructor, this creates a bug when sending emails with non-latin characters in the subject. this is a minor issue because you made it easy to override the action.

sfShibbolethPlugin needs to be linted for Symfony 1.4 compliance. Right now the filter chain is probably wrong for 1.4. Also make sure there's no select_tag nonsense.

1. I have a page under About called Staff. 2. I give that page a custom slug called /our-awesome-staff. 3. I decide to move that page underneath the contact section. 4. Now the slug is /contact/our-awesome-staff. This isn't what I wanted!

The redirect still works for this kind of situation, but we should avoid rewriting these custom slugs.

Right now the minifier uses the default caching behavior of the server, just as regular files in web/js or web/css would. This isn't terrible, it doesn't make things any worse than they already were. However it would be much better to have .htaccess directives specifying that the jssgz and cssgz files never expire so you can come back to the site without paying a penalty tomorrow.

The trick is making sure you don't get stuck with old versions if they *are* updated. You can do that by keeping a cache version string (a guid) in the asset-cache folder or perhaps someplace less public like data/a_writable. Delete that in the symfony cc hook. When it doesn't yet exist, make sure that you read it after generating and renaming the file just in case someone else won the race to rename it.

Thanks to pghoratiu.

I can't click on 'admin' (or any other user I sign in as). There is no way to reset the password unless I use the forgot password link.

/frontend_dev.php/uploads/media_items/stig-nygård.150.185.c.jpg : doesn't work

This request has been forwarded to a 404 error page by the action "a/show".
--
# at sfAction->forward404Unless()
in SF_ROOT_DIR/plugins/apostrophePlugin/lib/toolkit/BaseaTools.class.php line 498 ...

       495.   
       496.   static public function validatePageAccess(sfAction $action, $page)
       497.   {
       498.     $action->forward404Unless($page);
       499.     if (!$page->userHasPrivilege('view'))
       500.     {
       501.       // forward rather than login because referrers don't always

# at BaseaTools::validatePageAccess(object('aActions'), )
in SF_ROOT_DIR/plugins/apostrophePlugin/lib/action/BaseaActions.class.php line 54 ...

/index.php/uploads/media_items/stig-nygård.150.185.c.jpg : works

_accordion.php assigns ids to lists via:

id="a-nav-<?php echo $name ?>-<?php echo $nest ?>"

Thus, every ul at nest level greater than 0 will have the same id (i.e. a navigation of depth >= 2).

I tried to add a new page but because of the line 1544 in a.js, which is just appending the slug, I have a space in my slug so my form become invalid.

I am using different version of jQuery and it might be a problem with that... A way to fix it is to append .trim() function to ajax response before adding it to the path.

line 1543 to 1546 of a.js: $.get(optionsslugifyUrl?, { slug: $(titleField).val() }, function(data) {

slugField.val(optionsslugStem? + '/' + data.trim()); ajaxDirty = false;

});

I don't see why we can't add it ...

The current code (intended to keep caching happy) won't let you have two instances of the same email address. This is an issue on FM

When you upload and hide a file, it says "this office is private" instead of "this file is private" See the screenshot to compare.

Attachment 'ticket:1010: Screen shot 2011-04-04 at 4.00.51 PM.PNG]' does not exist.

PHP looks to 2 settings in php.ini to determine if an uploaded file is too big:

• upload_max_filesize (no single file can exceed this, defaults to 2MB)
• post_max_size (no post request can exceed this, even if you're uploading multiple files, defaults to 8MB)

The error currently returned for both of the above cases is: "FILE TOO LARGE. LIMIT IS 8M (or whatever the post_max_size is set to)". This error doesn't make sense if you're trying to upload a file that sits in between these limits, say a pdf that's 2.5MB.

We should be checking the error code in $_FILESuserfile?error? when our POST returns. If the error is UPLOAD_ERR_INI_SIZE, a file is too large.

All error codes can be found here:  http://php.net/manual/en/features.file-upload.errors.php

The error message must be adjusted in modules/aMedia/templates/_uploadMultiple.php

If an editor doesn't have permission to add or delete a page, they also don't have permission to publish or unpublish a page. However, the publish/unpublish button still shows up, it just doesn't allow the editor to save the page settings if they have touched the publish button.

Hi,

I detect a bug in sfForkedDoctrineApplyPlugin which is a fork of sfDoctrineApplyPlugin.

This bug is also in sfDoctrineApplyPlugin. The ticket on github is here:  https://github.com/fizyk/sfForkedDoctrineApplyPlugin/pull/38

Apostrophe developers have the bad habit of using both the data and uploads folder for file caches. The result is that the caches aren't cleared by the clear cache task or require an explicit hook to be cleared.

Why reinvent the wheel?

I filed this as a defect because clear-cache does not clear all Apostrophe caches (e.g. new image cache).

In the admin, there should be the ability to take an entire site-wide snapshot with the click of a button.

"Take Site Snapshot Now."

It freezes a copy of the database in it’s current incarnation, slots, slot history, etc. everything. Not sure how to handle actual files.

Then if a user makes a huge amount of changes to their site, they could take another snapeshot and roll back to a previous site snapshot if needed.

Snapshots should be browse-able in a logged-out only view. They don’t need to log-in to a snapshot, because the point of it is to view content differences, not manage them.

Browsing a snapshot should absolutely should have a url structure that looks like:  http://snapshot11-06-2010.clientsdomain.com/

These subdomains would only be viewable to an admin logged-in.

Browsing to them not logged-in prompts a login.

A global bar sites at the top of the snapshot that says:

Browsing Snapshot 11 January 2010: – Restore Site from this Snapshot – Delete this Snapshot – Download Snapshot to File – Import / Load Snapshot from File – Cancel / Leave

It should be possible to disable history for a singleton slot or an area via an option in the template or layout.

If constraints are in place, reject uploads that don't meet them with a clear and compassionate message. Later we'll offer gravity or even real cropping.

The current behavior (we accept it, but you don't see it; there's a message at the top of the page about constraints in general, but it was there before you clicked 'add") is too confusing.

We've seen this problem with client projects.

If you call $this->logSection() from inside a task, it will respect color coding and wrap your messages inside your task namespace. This is good symfony practice and we should be following it with all of our tasks.

I wrote a new task to address a specific use case : having massively re-organized the website structure prior to public release, I wanted the slugs to reflect that new structure (since no URIs had been made public, there were none to break), so I created a task very similar to the apostrophe:repair-tree task, called apostrophe:rebuild-slugs, which browses the tree and rebuilds the slug paths as it goes.

The code is provided as a patch (see attachment). The paths are relative to the svn.apostrophe.org root. I hope it is adequate, being the first patch I ever made.

See also:  http://groups.google.com/group/apostrophenow/browse_thread/thread/fe08fe759eb7b289

I put something like this in my template:

<h2><?php a_slot('headline', 'aText'); ?></h2>

Why does it end up as <h2><p>the text i entered via editing</p></h2>

And the <p> tag is written to the database. An empty edit field? Ends up as <p></p>.

How do I make aText be *real* plaintext?

As a workaround for now I tried this: <h2><?php a_slot('headline', 'aText', array('allowed-tags' => '<pre>')) ?></h2>

to have <p> removed.

Didn't work.

Versions: symfony -- via svn external from  http://svn.symfony-project.com/branches/1.4 apostrophePlugin - branches/1.4 as well.

Thanks,

-Lukas

Many Apostrophe components, such as aHtml, aRouteTools, aString, etc. do not extend BaseaXXX versions of themselves. As these calls are often embedded deep inside of other classes, it is virtually impossible to alter their functionality.

Apostrophe has clearly made an effort to be extensible, this is a small change that would help a lot.

 http://trac.apostrophenow.org/changeset/3399

The jury is out on whether this makes sense with engines in the picture or duplicates their functionality. If we used it, it would be a 1.6 kind of thing

It would be useful to have a set of allowed class names list in app.yml

Similar to how we have allowed_tags, allowed_attributes, allowed_styles

This will help with cleanup of unwanted MSWord styles etc that come through pastes.

 http://forum.symfony-project.org/index.php?t=rview&goto=92774&th=25217

We should systematically use the correct separator in our http_build_query calls depending on whether we're building a link in a tag (&amp;) or a redirect URL (&).

We should do this in the trunk and try to deliver it for 1.1, at which point we should remove the override of arg_separator.output that currently appears in .htaccess in the sandbox.

We should not do this in 1.0 stable because the override is 100% effective (just a little bit non-standards-compliant when it appears in HTML markup) and requires no potentially bug-introducing code changes.

When I upload a photo and add a title to it, it changes the name of the file. If I use a accents in the title, the image can't be finded because the new name.

example: upload a photo and add to title: "Títol" -> the system rename file to títol.original.jpg but the link is:

/uploads/media_items/t%C3%ADtol.original.jpg

and can't find it.

Joan Teixidó

If you use the placeholder and options\['width'\] is not set and options\['height'\] either, it errors out because the options\['height'\] setting uses option\s['width­'\] in it's calculation : it is : $height = (($options\['width'\]) ? floor($options\['width'\]*.56):'100px; as $width was calculate prior and is available (and = to options\['width'\] anyway if exists) it should be: $height = $options\['height'\].'px;' : $height = (($width) ? floor($width*.56):'100px;');

I downloaded an installed the sandbox, but i cannot reoganize the structure after clicking on "Struktur ändern" the little Windows below remains with that info "Benutze drag und drop um die Struktur der Site zu verändern." but no site structure.

I got a response on that at Google groups from a spanish guy (don't know if he wants me to tell his name) He told me to change the title of the Home page in Page Settings. I did change it fom "Home" to "Homepage" and after that I could change the structure. Many thanx to the spanish guy who helped me out.

Tom,

The javascript for variants is very verbose. Let's optimize/abstract this into a single function or class instead of having what we have now echo with every variant menu.

<script type="text/javascript" charset="utf-8">
 $(document).ready(function() {
   <?php // When the link to activate an inactive variant is clicked... ?>
   $('<?php echo "#a-$pageid-$name-$permid-variant-$variant-inactive a" ?>').click(function() {
   <?php // Add the loading class... ?>
   $('<?php echo "#a-$pageid-$name-$permid-variant ul.a-variant-options" ?>').addClass('loading');		
   <?php // Hide the active state of whatever variant was active (by brute force)... ?>			
   $('<?php echo "#a-$pageid-$name-$permid-variant ul.a-variant-options li.active" ?>').hide();
   <?php // Show all the inactive states... ?>
   $('<?php echo "#a-$pageid-$name-$permid-variant ul.a-variant-options li.inactive" ?>').show();
   <?php // And then show the one active state that is newly appropriate ?>
   $('<?php echo "#a-$pageid-$name-$permid-variant-$variant-active" ?>').show();
   <?php // And hide the corresponding inactive state ?>
   $('<?php echo "#a-$pageid-$name-$permid-variant-$variant-inactive" ?>').hide();
});
   $('<?php echo "#a-$pageid-$name-$permid-variant" ?>').children("ul.a-variant-options").hide();
 });
</script>

This unnecessary obfuscates which CSS file styles are coming from. Instead, I would propose simply appending .css to the end of the file name after it is processed.

It would be nice to wrap the jQuery function inside of a_get_js_calls with the more portable "jQuery" method rather than the shorthand "$". It's just a few more characters and allows developers to use other libraries that use the $-function. jQuery is my favorite but we have some legacy js code that relies on prototype.js, and it'd be nice to be able to use that along side apostrophe.

see:  http://trac.apostrophenow.org/browser/plugins/apostrophePlugin/branches/1.5/lib/helper/aHelper.php#L443

In other words, update...

function a_get_js_calls()
{
  $html = '';
  if (count(aTools::$jsCalls))
  {
    $html .= '<script type="text/javascript" charset="utf-8">' . "\n";
    $html .= '$(function() {' . "\n";
    foreach (aTools::$jsCalls as $call)
    {
      $html .= _a_js_call($call['callable'], $call['args']);
    }
    $html .= '});' . "\n";
    $html .= '</script>' . "\n";
  }
  return $html;
}

with

function a_get_js_calls()
{
  $html = '';
  if (count(aTools::$jsCalls))
  {
    $html .= '<script type="text/javascript" charset="utf-8">' . "\n";
    $html .= '(function($) {' . "\n";
    foreach (aTools::$jsCalls as $call)
    {
      $html .= _a_js_call($call['callable'], $call['args']);
    }
    $html .= '})(jQuery);' . "\n";
    $html .= '</script>' . "\n";
  }
  return $html;
}

The last step then would be to update a.js to pass in the $-function as a parameter.

// a.js
function aConstructor($)
...
window.apostrophe = new aConstructor(jQuery);

With those two changes I'm able to use legacy javascript libraries just fine.

We should create a command line script that will allow us to nuke the history when we deliver a site to production. In case we've left lorems or anything in the history, we can give clients a clean project.